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

Provide health status for networking

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • Networking health status
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      As a cluster admin or SRE, I would like a quick way to know if my networking infrastructure is healthy or not.

      Why is this important?

      I want to know the reliability of my network.  Today, it provides some insights, but it doesn't evaluate and tell me whether it is good, neutral, or bad, or whether some action needs to be taken.

      Planning Done Checklist

      • Define the initial set of areas that it will provide health status for.  For example, the initial phase could be in areas that Network Observability has information on, such as health status for traffic rates, latency, packet drops, and DNS errors.  Ultimately, this should go beyond flows and towards general networking.
      • Decide how it will show the health status (e.g. red, yellow, green).
      • Define the criteria for the different health status states (e.g. red, yellow, green).
      • Decide where this would be shown.  It seems better to be in Observe > Network Traffic, Overview tab than buried in the "NetObserv" dashboard under Observe > Dashboards.

              Unassigned Unassigned
              stlee@redhat.com Steven Lee
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: