[ML] Add an important note about a gotcha with the delayed data check #104725
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Recently a user saw spurious delayed data warnings. These turned out to be due to accidentally setting `summary_count_field` to a field that was always zero. This meant that every document was considered delayed.
droberts195
added
>docs
|
Documentation preview: |
elasticsearchmachine
added
Team:Docs
|
Pinging @elastic/ml-core (Team:ML) |
|
Pinging @elastic/es-docs (Team:Docs) |
szabosteve
reviewed
Jan 25, 2024
docs/reference/ml/anomaly-detection/ml-delayed-data-detection.asciidoc
Outdated
Show resolved
Hide resolved
…asciidoc Co-authored-by: István Zoltán Szabó <[email protected]>
szabosteve
reviewed
Jan 25, 2024
| ==== | ||
| As the `doc_count` from an aggregation is compared with the | ||
| bucket results of the job, the delayed data check will not work correctly in the | ||
| following cases: |
There was a problem hiding this comment.
Suggested change
| following cases: | |
| following cases: | |
💚 Backport successful
|
droberts195
added a commit
to droberts195/elasticsearch
that referenced
this pull request
Jan 25, 2024
…elastic#104725) Recently a user saw spurious delayed data warnings. These turned out to be due to accidentally setting `summary_count_field` to a field that was always zero. This meant that every document was considered delayed.
henningandersen
pushed a commit
to henningandersen/elasticsearch
that referenced
this pull request
Jan 25, 2024
…elastic#104725) Recently a user saw spurious delayed data warnings. These turned out to be due to accidentally setting `summary_count_field` to a field that was always zero. This meant that every document was considered delayed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Recently a user saw spurious delayed data warnings. These turned out to be due to accidentally setting
summary_count_fieldto a field that was always zero. This meant that every document was considered delayed.