浏览代码

[DOCS] Clarify impact of delayed data in anomaly detection (#66816)

Co-authored-by: Benjamin Trent <ben.w.trent@gmail.com>
Lisa Cawley 4 年之前
父节点
当前提交
eff9dfc3a4
共有 1 个文件被更改,包括 3 次插入3 次删除
  1. 3 3
      docs/reference/ml/anomaly-detection/ml-delayed-data-detection.asciidoc

+ 3 - 3
docs/reference/ml/anomaly-detection/ml-delayed-data-detection.asciidoc

@@ -2,8 +2,9 @@
 [[ml-delayed-data-detection]]
 = Handling delayed data
 
-Delayed data are documents that are indexed late. That is to say, it is data
-related to a time that the {dfeed} has already processed.
+Delayed data are documents that are indexed late. That is to say, it is data 
+related to a time that your {dfeed} has already processed and it is therefore
+never analyzed by your {anomaly-job}.
 
 When you create a {dfeed}, you can specify a
 {ref}/ml-put-datafeed.html#ml-put-datafeed-request-body[`query_delay`] setting.
@@ -50,4 +51,3 @@ action to consider is to increase the `query_delay` of the datafeed. This
 increased delay allows more time for data to be indexed. If you have real-time
 constraints, however, an increased delay might not be desirable. In which case,
 you would have to {ref}/tune-for-indexing-speed.html[tune for better indexing speed].
-