-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
None
-
False
-
-
False
-
5
-
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.