[DOCS] Alerts-as-data for anomaly detection rules #100864
Merged
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
lcawl
added
>docs
|
Documentation preview: |
|
Pinging @elastic/ml-core (Team:ML) |
elasticsearchmachine
added
Team:Docs
|
Pinging @elastic/es-docs (Team:Docs) |
szabosteve
approved these changes
Oct 17, 2023
💚 Backport successful
|
lcawl
added a commit
to lcawl/elasticsearch
that referenced
this pull request
Oct 17, 2023
lcawl
added a commit
that referenced
this pull request
Oct 17, 2023
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.
Relates to elastic/kibana#165958
This PR uses new screenshots that are automated in elastic/kibana#168900.
It updates Generating alerts for anomaly detection jobs to reflect the new types of action frequencies available in anomaly detection alert rules.
Since anomaly detection jobs health rules do not have the same options, I've changed the layout of the page such that the "actions" sections are nested under the rule types. Likewise, since transform health rules do not have the same options, I've removed the tagged region that was re-using content across these pages.
@szabosteve If you think I should move the rule-specific action variable sections under the rule-specific sections too or just split this into two separate pages, lmk!