Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ML] Add an important note about a gotcha with the delayed data check #104725

Merged
merged 4 commits into from
Jan 25, 2024
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,16 @@ for the periods where these delays occur:
[role="screenshot"]
image::images/ml-annotations.png["Delayed data annotations in the Single Metric Viewer"]

IMPORTANT: Because we are comparing `doc_count` from an aggregation with the
job's bucket results, the delayed data check will not work correctly if the
job's datafeed is using aggregations and its `analysis_config` does not have
its `summary_count_field_name` set to `doc_count`, or if your job is _not_
using aggregations and `summary_count_field_name` is set to anything. If your
job's datafeed is using aggregations then it's highly likely that your
`summary_count_field_name` should be `doc_count`. If `summary_count_field_name`
is set at all, and is _not_ set to `doc_count`, then you must disable the
delayed data check for that job.

droberts195 marked this conversation as resolved.
Show resolved Hide resolved
There is another tool for visualizing the delayed data on the *Annotations* tab
in the {anomaly-detect} job management page:

Expand Down