Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-2411

Alert with empty NS doesn't navigate to actual Alerting rule

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Operator
    • None
    • None
    • NetObserv - Sprint 278
    • None
    • None
    • None

      Description of problem:

      When navigating to Alerts with empty NS, it show "Alert Not Found"
      
       !image-2025-09-19-10-20-22-585.png|thumbnail! 
      
      See discussion here: https://github.com/netobserv/network-observability-operator/pull/1790#issuecomment-3286477660
      
      

      Steps to Reproduce:

      1. Enable DNSTracking feature
      2. Deploy pods resulting in dnserrors.
      3. 
      

      Actual results:

      Alert with empty ns shows up in Global menu, when navigating to the alerting rule it shows Alerting Not found.
      
      

      Expected results:

      Users should be navigated to the Alerting rule successfully.

       

              lberetta@redhat.com Leandro Beretta
              rhn-support-memodi Mehul Modi
              None
              None
              None
              Amogh Rameshappa Devapura Amogh Rameshappa Devapura
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: