-
Notifications
You must be signed in to change notification settings - Fork 25.5k
Adds note on anomaly detection alert behaviour #126102
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
Conversation
Documentation preview: |
Pinging @elastic/es-docs (Team:Docs) |
alert status changes, or at a custom action interval). For {anomaly-detect} | ||
alert status changes, or at a custom action interval). | ||
|
||
When you use an email action with an {anomaly-detect} rule, the alert includes only the top three anomalous records or influencers detected during the check interval. This behavior ensures that the alert remains concise by highlighting the most significant anomalies based on their scores. |
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.
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.
LGTM unless @darnautov thinks otherwise. :)
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.
LGTM
* Adds note on anomaly detection alert behaviour * Fixes attribute * Relocating the addition * Fixes based on feedback
* Adds note on anomaly detection alert behaviour * Fixes attribute * Relocating the addition * Fixes based on feedback
* Adds note on anomaly detection alert behaviour * Fixes attribute * Relocating the addition * Fixes based on feedback
This PR updates the anomaly detection alerting documentation to clarify that email alerts include only the top three anomalous records or influencers.
Related issue: https://github.com/elastic/search-docs-team/issues/277