-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Allow users to define burn rate windows using budget consumed #170996
[SLO] Allow users to define burn rate windows using budget consumed #170996
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there is one test on the min burn rate threshold to change, but otherwise, it looks good!
x-pack/plugins/observability/public/components/burn_rate_rule_editor/budget_consumed.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/observability/public/components/burn_rate_rule_editor/budget_consumed.tsx
Show resolved
Hide resolved
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
x-pack/plugins/observability/public/components/burn_rate_rule_editor/budget_consumed.tsx
Outdated
Show resolved
Hide resolved
@simianhacker Looks good! Is there a reason you changed from first decimal (14.4) to second decimal (14.40)? I was wondering if it is better to have the toggle on top of the form vs at the bottom. @maciejforcone What do you think? I guess Maciej will cover the positioning of the configuration(toggle) as part of this issue, so I don't want to block this PR. |
I played a bit with the form, deleting and readding a window. I just want to confirm if the default values for the new window are good or if we need to revisit. Screen.Recording.2023-11-10.at.21.03.19.mov |
@mgiota I switched to 2 decimal places because when you configure via budget consumed, we needed the extra decimal for the 7 day 1 hour burn rate for |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Module Count
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
Summary
This PR fixes #170854 and #170859 by allowing the user to define the burn rate windows using either a burn rate threshold or the % of budget consumed by the time the alert triggers. This PR also adds the budget consumed to the help text below the burn rate window definition. I also changed the behavior to hide the window definitions until the Selected SLO is chosen since we need the SLO for the calculations.
Screen.Recording.2023-11-09.at.5.14.59.PM.mov