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.

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

[SLO] Add "Last 24 Hours" of source events to the SLO Detail Page for KQL Indicator #153952

Open
simianhacker opened this issue Mar 29, 2023 · 1 comment
Labels
Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge"

Comments

@simianhacker
Copy link
Member

simianhacker commented Mar 29, 2023

Underneath the Error Budget chart on a Custom KQL SLI, I would love to see a histogram of good events over bad events for the last 24 hours along with an embedded discover view of the last 500 "bad" events. The reason I think the last 24 hours of events is important is because that's the maximum lookback of the "Burn Rate" alert. This will make it easier to see what's going on if a user is exploring SLOs and notices a breaching SLO; they might want to start investigating right there. Same thing should be applied to the Burn Rate Alert detail page.

image

@simianhacker simianhacker added the Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge" label Mar 29, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/actionable-observability (Team: Actionable Observability)

@emma-raffenne emma-raffenne added this to the 8.10 milestone Aug 7, 2023
@emma-raffenne emma-raffenne removed this from the 8.10 milestone Aug 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge"
Projects
None yet
Development

No branches or pull requests

3 participants