-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
feat(slo): improve burn rate panel #197339
feat(slo): improve burn rate panel #197339
Conversation
d857b42
to
84c47d4
Compare
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
|
💚 Build Succeeded
Metrics [docs]Async chunks
History
cc @kdelemme |
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.
Smoke testing and code review LGTM !!
Starting backport for target branches: 8.x |
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
(cherry picked from commit a5b266c)
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
# Backport This will backport the following commits from `main` to `8.x`: - [feat(slo): improve burn rate panel (#197339)](#197339) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kevin Delemme","email":"kevin.delemme@elastic.co"},"sourceCommit":{"committedDate":"2024-11-13T17:52:19Z","message":"feat(slo): improve burn rate panel (#197339)","sha":"a5b266c45b7db8821281a2325d919b6fdf679618","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-management","v8.17.0"],"number":197339,"url":"https://github.com/elastic/kibana/pull/197339","mergeCommit":{"message":"feat(slo): improve burn rate panel (#197339)","sha":"a5b266c45b7db8821281a2325d919b6fdf679618"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/197339","number":197339,"mergeCommit":{"message":"feat(slo): improve burn rate panel (#197339)","sha":"a5b266c45b7db8821281a2325d919b6fdf679618"}},{"branch":"8.x","label":"v8.17.0","labelRegex":"^v8.17.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
Resolves #195139
🌸 Summary
The history details page was using the burn rate component but only to show the error rate chart named as "burn rate", which is incorrect. I've removed the usage of that component, and only used the ErrorRateChart on that page. I was able to refactor this component slightly to remove the need to provide a
selectedTabId
.Then, I changed the burnRatePanel component to use both the short and long window burn rates in order to handle cases like recovering/increasing burn rate.
Testing
node x-pack/scripts/data_forge.js --events-per-cycle 50 --lookback now-7d --dataset fake_stack --install-kibana-assets --kibana-url http://localhost:5601/kibana