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

Extend health to non-netobserv metrics such as ingress alerts

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • None
    • None
    • NetObserv - Sprint 276, NetObserv - Sprint 277, NetObserv - Sprint 278, NetObserv - Sprint 279, NetObserv - Sprint 280, NetObserv - Sprint 281, NetObserv - Sprint 282, NetObserv - Sprint 283

      Review other (non-netobserv) metrics available out there, and see if we can leverage our alerting+health mechanism on them too

      E.g:

      • ingress errors (haproxy_server_http_responses_total)
      • ingress performance degrading (? haproxy_server_http_average_response_latency_milliseconds)
      • ingress connections coming close to capacity

      To start with, we should probably use RecordingRules rather than Alerts here, to make sure we don't produce unwanted noise.

       

      See also these RFEs: RFE-2935, RFE-8004 

              lberetta@redhat.com Leandro Beretta
              jtakvori Joel Takvorian
              None
              None
              Mehul Modi Mehul Modi
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: