Alert Condition based SLOs

[sarabartell]

Summary

Currently you can only assign an alert driven SLO by policy. However that would mean you need a 1:1:1 on entity - condition - policy for these alerts to be accurate. Example - entity: app1, condition: throughput high, policy: app1 high throughput

Desired Behaviour

It would be great if we could select by condition under the policy. Example - Policy: Backend, conditions: high CPU, high response time, low apdex

If you have policies grouped by app or function there needs to be a way to specify which condition we would like to pull out of the policy.

Possible Solution

Adding one more layer to the form to select the condition under the policy if needed. The condition name is being captured in the JSON payload from alerts already.

[danifitz]

+1 for this - currently only being able to create an alert-driven SLO by policy is quite limiting and requires customers to have their alerts structured in a certain way. If you could specify the condition name, that would allow to be more fine-grained.

For example, if customer has a policy called US Synthetic Checks and this policy contains all the conditions for their uptime synthetic checks, it is not possible to create an SLO which only measures availability of a particular service/endpoint.