The burn rate rule provides a number of context variables for crafting a connector notification via rule actions. An example of this messaging is seen here, in a Slack bot:

From @sebgl, we have the following enhancement request:

I think what I’d like to see in the alert message is something like:

LOW: at this rate, the 30 days SLO will be consumed in 5 days. p50 request latency for the past 72h: 1.3 sec (30 bad events out of 45).

Which would contain both:

• some time duration to better understand how bad things are (more explicit than “a burn rate of 2.1”)
• the actual value of the metric the SLO is based on (or, assuming that’s hard, the ratio of good vs bad events)
  image.png

Based on this and other feedback, we should also consider updating the auto-configured "reason" message for burn rate rules to be clearer.