Open kroperea opened 4 years ago
Thx for this - I completely agree with the Alert workflow - it is way too much burden to set these slos up at scale. I've been waiting for an API enhancement to get rig of the web-hook workaround and query the alert statuses on entities directly. I am going to investigate the timeline on that functionality and see how far out we are.
Will update on my plan to address this once we have an idea of the alert api graphql improvements
Summary
Right now to create an SLO, we have to create an Alert policy and a condition. 1 SLO x 1 alert policy x 1 condition
Desired Behaviour
We would like to group all SLOs for a specific entity under one single Alert Policy and have one condition per each SLO.
e.g If the entity X has 3 SLOs: ART, RPM and ERROR rate - we would like to have 1 alert policy with 3 conditions, instead of having to create 3 alert policies and 3 conditions.
Alert Policy X: SLOs-entityX Condition1: ART Condition2: RPM Condition3: ERROR rate
Additional context
We have too many applications and defining individual alert policies for each SLO would create too much noise and make it hard to search for SLOs of a specific application.
Requesting on behalf of SAP CONCUR.