Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[SLO] Add SLO summary context to the burn rate alert #183747

Closed
kdelemme opened this issue May 17, 2024 · 0 comments · Fixed by #184471
Closed

[SLO] Add SLO summary context to the burn rate alert #183747

kdelemme opened this issue May 17, 2024 · 0 comments · Fixed by #184471
Assignees
@kdelemme
Labels
Team:obs-ux-management Observability Management User Experience Team

Comments

@kdelemme
Copy link
Contributor

kdelemme commented May 17, 2024 •
edited

Summary

This is an updated issue summary after more discussion on slack: https://elastic.slack.com/archives/C044PV8EJ4X/p1716968663913879

It seems it would be useful for folks to have access to the SLO status, SLI and error budget remaining/consumed whenever an alert is fired. We can provide this contextual information by looking up the SLO in the SLO summary index. The summary data might be "slightly" delayed, but we believe this is a fine trade-off.
@kdelemme kdelemme added the Team:obs-ux-management Observability Management User Experience Team label May 17, 2024
This was referenced May 17, 2024
Closed
Open
@kdelemme kdelemme self-assigned this May 21, 2024
@kdelemme kdelemme changed the title [SLO] Add errorBudgetExhaustionTime context variable in SLO burn rate rule [SLO] Add SLO summary context to the burn rate alert May 29, 2024
@kdelemme kdelemme mentioned this issue May 29, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kdelemme kdelemme

Labels
Team:obs-ux-management Observability Management User Experience Team
Projects
None yet
Milestone
No milestone
1 participant
@kdelemme