Skip to content

Commit

Permalink
[DOCS] Clarify impact of delayed data in anomaly detection (#66816) (#…
Browse files Browse the repository at this point in the history
…67041)

Co-authored-by: Benjamin Trent <[email protected]>
  • Loading branch information
lcawl and benwtrent authored Jan 5, 2021
1 parent e9b798b commit 6175e18
Showing 1 changed file with 3 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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].

0 comments on commit 6175e18

Please sign in to comment.