github-mirrors/elasticsearch
1
0
Fork 0
mirror of https://github.com/elastic/elasticsearch.git synced 2025-04-24 23:27:25 -04:00
Code Issues Projects Releases Packages Wiki Activity

[DOCS] Update transform and anomaly detection rule creation steps (#107975)

Browse source
This commit is contained in:
Lisa Cawley 2024-05-07 07:52:45 -07:00 • committed by GitHub
parent e8cb8c67d5
commit a079cdc17d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
4 changed files with 10 additions and 18 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/reference/ml/anomaly-detection/ml-configuring-alerts.asciidoc
View file

@ -27,12 +27,7 @@ TIP: If you have created rules for specific {anomaly-jobs} and you want to
monitor whether these jobs work as expected, {anomaly-jobs} health rules are monitor whether these jobs work as expected, {anomaly-jobs} health rules are
ideal for this purpose. ideal for this purpose.
In *{stack-manage-app} > {rules-ui}*, you can create both types of {ml} rules: In *{stack-manage-app} > {rules-ui}*, you can create both types of {ml} rules.
[role="screenshot"]
image::images/ml-rule.png["Creating a new machine learning rule",500]
// NOTE: This is an autogenerated screenshot. Do not edit it directly.
In the *{ml-app}* app, you can create only {anomaly-detect} alert rules; create In the *{ml-app}* app, you can create only {anomaly-detect} alert rules; create
them from the {anomaly-job} wizard after you start the job or from the them from the {anomaly-job} wizard after you start the job or from the
{anomaly-job} list. {anomaly-job} list.

BIN
docs/reference/ml/images/ml-rule.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 116 KiB

BIN
docs/reference/transform/images/transform-rule.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 81 KiB

21
docs/reference/transform/transform-alerts.asciidoc
View file

@ -18,18 +18,19 @@ refer to
You can create {transform} rules under **{stack-manage-app} > {rules-ui}**. You can create {transform} rules under **{stack-manage-app} > {rules-ui}**.
. On the *Create rule* window, give a name to the rule and optionally provide . Click *Create rule* and select the {transform} health rule type.
tags. Select the {transform} health rule type:
+ . Give a name to the rule and optionally provide tags.
--
[role="screenshot"]
image::images/transform-rule.png["Creating a transform health rule",500]
// NOTE: This is screenshot is automatically generated. Do not edit it directly.
--
. Select the {transform} or {transforms} to include. You can also use a special . Select the {transform} or {transforms} to include. You can also use a special
character (`*`) to apply the rule to all your {transforms}. {transforms-cap} character (`*`) to apply the rule to all your {transforms}. {transforms-cap}
created after the rule are automatically included. created after the rule are automatically included.
+
--
[role="screenshot"]
image::images/transform-check-config.png["Selecting health check",500]
// NOTE: This is screenshot is automatically generated. Do not edit it directly.
--
. The following health checks are available and enabled by default: . The following health checks are available and enabled by default:
+ +
@ -41,10 +42,6 @@ _{transform-cap} is not started_::
_Unhealthy {transform}_:: _Unhealthy {transform}_::
Get alerts when a {transform} has an unhealthy status. Get alerts when a {transform} has an unhealthy status.
The notification message contains status details and related issues. The notification message contains status details and related issues.
[role="screenshot"]
image::images/transform-check-config.png["Selecting health check",500]
// NOTE: This is screenshot is automatically generated. Do not edit it directly.
-- --
. Set the check interval, which defines how often to evaluate the rule conditions. . Set the check interval, which defines how often to evaluate the rule conditions.