From c5c8ef208caaff04349e894795309f427891070e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?= Date: Wed, 2 Jun 2021 17:16:43 +0200 Subject: [PATCH] [DOCS] Removes Kibana charts-related advise about agg interval and bucket span. (#73673) (#73677) --- .../anomaly-detection/ml-configuring-aggregations.asciidoc | 7 ------- 1 file changed, 7 deletions(-) diff --git a/docs/reference/ml/anomaly-detection/ml-configuring-aggregations.asciidoc b/docs/reference/ml/anomaly-detection/ml-configuring-aggregations.asciidoc index 155b97d0f36a5..7970eacff6407 100644 --- a/docs/reference/ml/anomaly-detection/ml-configuring-aggregations.asciidoc +++ b/docs/reference/ml/anomaly-detection/ml-configuring-aggregations.asciidoc @@ -53,13 +53,6 @@ Viewer** nor the **Anomaly Explorer** can plot and display an anomaly chart for the job. In these cases, the charts are not visible and an explanatory message is shown. -When the aggregation interval of the {dfeed} and the bucket span of the job -don't match, the values of the chart plotted in both the **Single Metric -Viewer** and the **Anomaly Explorer** differ from the actual values of the job. -To avoid this behavior, make sure that the aggregation interval in the {dfeed} -configuration and the bucket span in the {anomaly-job} configuration have the -same values. - Your {dfeed} can contain multiple aggregations, but only the ones with names that match values in the job configuration are fed to the job.