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] Allow users to define burn rate windows using budget consumed #170996

Merged
merged 7 commits into from Nov 11, 2023

Conversation

simianhacker
Copy link
Member

@simianhacker simianhacker commented Nov 10, 2023

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

@simianhacker simianhacker added release_note:enhancement Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge" Feature:SLO v8.12.0 Team:obs-ux-management Observability Management User Experience Team labels Nov 10, 2023
@apmmachine
Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
  • /oblt-deploy-serverless : Deploy a serverless Kibana instance using the Observability test environments.
  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@mgiota mgiota self-requested a review November 10, 2023 08:23
Copy link
Contributor

@kdelemme kdelemme left a 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!

@simianhacker simianhacker marked this pull request as ready for review November 10, 2023 16:18
@simianhacker simianhacker requested a review from a team as a code owner November 10, 2023 16:18
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

@mgiota
Copy link
Contributor

mgiota commented Nov 10, 2023

@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.

@mgiota
Copy link
Contributor

mgiota commented Nov 10, 2023

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

@simianhacker
Copy link
Member Author

@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 2% budget consumed which is 3.36x

@simianhacker simianhacker enabled auto-merge (squash) November 11, 2023 20:35
@simianhacker simianhacker merged commit 7923a96 into elastic:main Nov 11, 2023
28 checks passed
@kibana-ci
Copy link
Collaborator

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
observability 490 491 +1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
observability 1.1MB 1.1MB +1.9KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
observability 104.1KB 104.1KB +5.0B

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@kibanamachine kibanamachine added the backport:skip This commit does not require backporting label Nov 11, 2023
jillguyonnet pushed a commit to jillguyonnet/kibana that referenced this pull request Nov 16, 2023
…lastic#170996)

## Summary

This PR fixes elastic#170854 and
elastic#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.


https://github.com/elastic/kibana/assets/41702/26f795f3-47cb-45c6-8ba3-528c2d9c4094
@simianhacker simianhacker deleted the issue-170854-budget-consumed branch April 17, 2024 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting Feature:SLO release_note:enhancement Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge" Team:obs-ux-management Observability Management User Experience Team v8.12.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[SLO] Display Error Budget consumption in the Burn Rate Rule Form
7 participants