[Custom threshold][Alert details page] Deprecate feature flag for Custom threshold rule alert details page #176666
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
maryam-saeidi
added
release_note:feature
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
botelastic
bot
added
the
Team:obs-ux-management
|
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
XavierM
approved these changes
Feb 12, 2024
banderror
approved these changes
Feb 13, 2024
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Public APIs missing comments
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
kibanamachine
added
v8.13.0
backport:skip
CoenWarmer
pushed a commit
to CoenWarmer/kibana
that referenced
this pull request
Feb 15, 2024
…tom threshold rule alert details page (elastic#176666) Closes elastic#153867 ## Summary This PR deprecates the following feature flag for the Custom threshold rule alert details page. ``` xpack.observability.unsafe.alertDetails.observability.enabled ```  ## 🧪 How to test - Remove `xpack.observability.unsafe.alertDetails.observability.enabled` from Kibana config - Create a custom threshold rule - Check the alert details page - From alert table's flyout - From action variables - Add `xpack.observability.unsafe.alertDetails.observability.enabled` to the Kibana config - You should see the following warning ``` [WARN ][config.deprecation] You no longer need to configure "xpack.observability.unsafe.alertDetails.observability.enabled". ``` ## Release note - Adds a dedicated alert details page for the Custom threshold rule. When a threshold is breached, the alert details page helps users quickly triage the alert, showing details and context around that alert such as when the alert started, its current status, and other details. When a log rate-based threshold is breached, the alert details page also includes an automatic log rate analysis depicting shared characteristics among log messages contributing to this change and in-context Observability AI Assistant to provide further insight and remedy suggestions.
fkanout
pushed a commit
to fkanout/kibana
that referenced
this pull request
Mar 4, 2024
…tom threshold rule alert details page (elastic#176666) Closes elastic#153867 ## Summary This PR deprecates the following feature flag for the Custom threshold rule alert details page. ``` xpack.observability.unsafe.alertDetails.observability.enabled ```  ## 🧪 How to test - Remove `xpack.observability.unsafe.alertDetails.observability.enabled` from Kibana config - Create a custom threshold rule - Check the alert details page - From alert table's flyout - From action variables - Add `xpack.observability.unsafe.alertDetails.observability.enabled` to the Kibana config - You should see the following warning ``` [WARN ][config.deprecation] You no longer need to configure "xpack.observability.unsafe.alertDetails.observability.enabled". ``` ## Release note - Adds a dedicated alert details page for the Custom threshold rule. When a threshold is breached, the alert details page helps users quickly triage the alert, showing details and context around that alert such as when the alert started, its current status, and other details. When a log rate-based threshold is breached, the alert details page also includes an automatic log rate analysis depicting shared characteristics among log messages contributing to this change and in-context Observability AI Assistant to provide further insight and remedy suggestions.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #153867
Summary
This PR deprecates the following feature flag for the Custom threshold rule alert details page.
🧪 How to test
xpack.observability.unsafe.alertDetails.observability.enabledfrom Kibana configxpack.observability.unsafe.alertDetails.observability.enabledto the Kibana configRelease note
Adds a dedicated alert details page for the Custom threshold rule. When a threshold is breached, the alert details page helps users quickly triage the alert, showing details and context around that alert such as when the alert started, its current status, and other details. When a log rate-based threshold is breached, the alert details page also includes an automatic log rate analysis depicting shared characteristics among log messages contributing to this change and in-context Observability AI Assistant to provide further insight and remedy suggestions.