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.

Sign up for GitHub

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

[DOCS] Simplifies composite aggregation recommendation #89878

Merged
merged 2 commits into from
Sep 7, 2022
Merged

[DOCS] Simplifies composite aggregation recommendation #89878

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dc877d2
[DOCS] Simplifies composite aggregation recommendation.
szabosteve Sep 7, 2022
8aa102a
[DOCS] Adds back snippet and fixes a typo.
szabosteve Sep 7, 2022
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
17 changes: 6 additions & 11 deletions docs/reference/ml/anomaly-detection/ml-configuring-aggregations.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,10 @@ such as `terms`.
the name of the field that contains the count of raw data points that have been
aggregated. It applies to all detectors in the job.

* The influencers or the partition fields must be included in the aggregation of
your {dfeed}, otherwise they are not included in the job analysis. For more
information on influencers, refer to <<ml-ad-influencers>>.


[discrete]
[[aggs-interval]]
Expand Down Expand Up @@ -83,11 +87,8 @@ type of analysis.
<<ml-rare-functions,rare>> functions, set the interval to the same value as the
bucket span.

* By default, {es} limits the maximum number of terms returned to 10000. For
high cardinality fields, the query might not run. It might return errors related
to circuit breaking exceptions that indicate that the data is too large. When
you use a terms aggregation and the cardinality of a term is high but still
significantly less than your total number of documents, use
* If you have multiple influencers or partition fields or if your field
cardinality is more than 1000, use
{ref}/search-aggregations-bucket-composite-aggregation.html[composite aggregations].
+
--
Expand All @@ -109,12 +110,6 @@ GET .../_search
// NOTCONSOLE
--

* When you use a `term` aggregation to gather influencer or partition field
information, consider using a `composite` aggregation. It performs better than a
`date_histogram` with a nested `term` aggregation and also includes all the
values of the field instead of the top values per bucket. For more information
on influencers, refer to <<ml-ad-influencers>>.


[discrete]
[[aggs-using-date-histogram]]
Expand Down