From f539f11f465f5b07e4a5941e548285cbbf192b47 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?= Date: Tue, 23 Aug 2022 16:54:44 +0200 Subject: [PATCH] [DOCS] Resizes anomaly detection screenshot properly. (#89544) (#89552) --- .../ml/anomaly-detection/ml-configuring-alerts.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/ml/anomaly-detection/ml-configuring-alerts.asciidoc b/docs/reference/ml/anomaly-detection/ml-configuring-alerts.asciidoc index 5057efec24907..7afaf88081b20 100644 --- a/docs/reference/ml/anomaly-detection/ml-configuring-alerts.asciidoc +++ b/docs/reference/ml/anomaly-detection/ml-configuring-alerts.asciidoc @@ -61,7 +61,7 @@ You must select a type of {ml} result. In particular, you can create rules based on bucket, record, or influencer results. [role="screenshot"] -image::images/ml-anomaly-alert-severity.jpg["Selecting result type, severity, and test interval"] +image::images/ml-anomaly-alert-severity.jpg["Selecting result type, severity, and test interval", 500] For each rule, you can configure the `anomaly_score` that triggers the action. The `anomaly_score` indicates the significance of a given anomaly compared to