Skip to content

Conversation

@estherk15
Copy link
Contributor

What does this PR do? What is the motivation?

  • Add burn rate indicator information
  • Clean up white space

Merge instructions

Merge readiness:

  • Ready for merge

Rifa-Tamannaa and others added 2 commits November 7, 2025 09:22
Also updated SLO status pge to say SLO manage page instead
@estherk15 estherk15 requested a review from a team as a code owner November 7, 2025 14:36
@github-actions github-actions bot added the Images Images are added/removed with this PR label Nov 7, 2025
@estherk15 estherk15 changed the title Rifa/slo burn rate indicator SLO burn rate indicator Nov 7, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 7, 2025

Preview links (active after the build_preview check completes)

Modified Files

@cswatt cswatt self-assigned this Nov 7, 2025
Copy link
Contributor

@cswatt cswatt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good! I mainly just have one comment + some suggested expanded alt text


### SLO burn rate indicator

Burn rate indicators identify SLOs that are consuming their error budget faster than their configured target permits within the rolling 2-hour evaluation window. They appear next to the applicable SLO names on the [SLO manage page][2].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Burn rate indicators identify SLOs that are consuming their error budget faster than their configured target permits within the rolling 2-hour evaluation window. They appear next to the applicable SLO names on the [SLO manage page][2].
Burn rate indicators identify SLOs that are consuming their error budget faster than their configured target permits within the rolling 2-hour evaluation window. Burn rate indicators appear next to the applicable SLO names on the [SLO manage page][2].
  • Question on first sentence, because I see two different ways to interpret it:
    • Burn rate indicators use a rolling 2-hour evaluation window to evaluate which SLOs are having too many errors too quickly
    • SLOs permit a certain number of errors within a rolling 2-hour evaluation window, and burn rate indicators identify the ones that are having too many errors too quickly

tldr it's ambiguous what the within the rolling 2-hour evaluation window clause is referring to. I believe it should be the first interpretation, in which case maybe reword to Burn rate indicators identify (within a rolling 2-hour evaluation window) SLOs that are consuming their error budget faster than their configured target permits.? Inelegant suggestion here, I'll leave the rewording up to you.


Burn rate indicators identify SLOs that are consuming their error budget faster than their configured target permits within the rolling 2-hour evaluation window. They appear next to the applicable SLO names on the [SLO manage page][2].

{{< img src="/service_management/service_level_objectives/slo_burn_rate_indicator.png" alt="SLO burn rate indicator example" style="width:80%;" >}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
{{< img src="/service_management/service_level_objectives/slo_burn_rate_indicator.png" alt="SLO burn rate indicator example" style="width:80%;" >}}
{{< img src="/service_management/service_level_objectives/slo_burn_rate_indicator.png" alt="The SLO manage page in Datadog. A red icon appears next to the name of an SLO in the list. Mousing over the red icon displays a modal with further information, a burn rate visualization, and a link to the SLO's corresponding service page." style="width:80%;" >}}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Images Images are added/removed with this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants