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
[DOCS] Update transform and anomaly detection rule creation steps #107975
Conversation
Documentation preview: |
Pinging @elastic/ml-core (Team:ML) |
Pinging @elastic/es-docs (Team:Docs) |
|
||
. Select the {transform} or {transforms} to include. You can also use a special | ||
character (`*`) to apply the rule to all your {transforms}. {transforms-cap} | ||
created after the rule are automatically included. |
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.
"rule is" or "rules are"?
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.
That blurb appears as following in the preview, which I think looks right: "You can also use a special character (*) to apply the rule to all your transforms. Transforms created after the rule are automatically included."
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! Thank you!
Relates to elastic/kibana#175634
This PR updates https://www.elastic.co/guide/en/elasticsearch/reference/current/transform-alerts.html and https://www.elastic.co/guide/en/machine-learning/current/ml-configuring-alerts.html
In particular, it removes screenshots that are no longer accurate or necessary.