-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
None
-
False
-
-
False
-
Release Note Not Required
-
-
-
Pipelines Sprint Tekshift 32
Once the component metrics for each OSP component konflux_up availability metric are identified, we need to define SLO alerts to fire when those signals are unhealthy. These will be monitored in Tactical Status Page, here: https://tsp.status.redhat.com/service/P99JEYA and should result in notices to the #konflux-slo-alerts channel on Slack.
Acceptance Criteria
- All constituent metrics that compose OSP Component konflux_up signals are evaluated and SLO alerts are defined as appropriate to capture their failure modes, here: https://github.com/redhat-appstudio/o11y/tree/main/rhobs/alerting
- SLO alerts have been tested in staging and refined to minimize flapping
- Ensure new SLOs appear on Konflux SLOs dashboard (https://grafana.app-sre.devshift.net/d/rhtap-slos/konflux-slos?orgId=1&refresh=1h)