From 7ec8837f0beb4d1e9d27937e85d006ed0fe5ca05 Mon Sep 17 00:00:00 2001 From: ashwinkumar12345 Date: Wed, 24 Nov 2021 12:08:29 -0800 Subject: [PATCH] minor clarification Signed-off-by: ashwinkumar12345 --- _monitoring-plugins/ad/result-mapping.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_monitoring-plugins/ad/result-mapping.md b/_monitoring-plugins/ad/result-mapping.md index 8cbe8436..54d86705 100644 --- a/_monitoring-plugins/ad/result-mapping.md +++ b/_monitoring-plugins/ad/result-mapping.md @@ -194,7 +194,7 @@ If a detector detects an anomaly late, the result has the following additional f Field | Description :--- | :--- `past_values` | The actual input that triggered an anomaly. If `past_values` is null, the attributions or expected values are from the current input. If `past_values` is not null, the attributions or expected values are from a past input (for example, the previous two steps of the data [1,2,3]). -`approx_anomaly_start_time` | The approximate time of the actual input that triggers an anomaly. This field helps you understand when a detector flags an anomaly. If the data is not continuous, the actual time that the detector detects the anomaly can be earlier. Both single-stream and high-cardinality detectors don't query previous anomaly results because these queries are expensive operations, especially when a detector has a lot of entities. This is why the accuracy of this field is low. +`approx_anomaly_start_time` | The approximate time of the actual input that triggers an anomaly. This field helps you understand when a detector flags an anomaly. Both single-stream and high-cardinality detectors don't query previous anomaly results because these queries are expensive operations. The cost is especially high for high-cardinality detectors that might have a lot of entities. If the data is not continuous, the accuracy of this field is low and the actual time that the detector detects an anomaly can be earlier. ```json {