WARNING: Version 2.2 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
This functionality is in technical preview and may be changed or removed in a future release. Elastic will apply best effort to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
Pipeline aggregations work on the outputs produced from other aggregations rather than from document sets, adding information to the output tree. There are many different types of pipeline aggregation, each computing different information from other aggregations, but these types can be broken down into two families:
- A family of pipeline aggregations that is provided with the output of its parent aggregation and is able to compute new buckets or new aggregations to add to existing buckets.
- Pipeline aggregations that are provided with the output of a sibling aggregation and are able to compute a new aggregation which will be at the same level as the sibling aggregation.
Pipeline aggregations can reference the aggregations they need to perform their computation by using the
parameter to indicate the paths to the required metrics. The syntax for defining these paths can be found in the
buckets_path Syntax section below.
Pipeline aggregations cannot have sub-aggregations but depending on the type it can reference another pipeline in the
allowing pipeline aggregations to be chained. For example, you can chain together two derivatives to calculate the second derivative
(i.e. a derivative of a derivative).
Because pipeline aggregations only add to the output, when chaining pipeline aggregations the output of each pipeline aggregation will be included in the final output.
Most pipeline aggregations require another aggregation as their input. The input aggregation is defined via the
parameter, which follows a specific format:
AGG_SEPARATOR := '>' METRIC_SEPARATOR := '.' AGG_NAME := <the name of the aggregation> METRIC := <the name of the metric (in case of multi-value metrics aggregation)> PATH := <AGG_NAME>[<AGG_SEPARATOR><AGG_NAME>]*[<METRIC_SEPARATOR><METRIC>]
For example, the path
"my_bucket>my_stats.avg" will path to the
avg value in the
"my_stats" metric, which is
contained in the
"my_bucket" bucket aggregation.
Paths are relative from the position of the pipeline aggregation; they are not absolute paths, and the path cannot go back "up" the
aggregation tree. For example, this moving average is embedded inside a date_histogram and refers to a "sibling"
buckets_path is also used for Sibling pipeline aggregations, where the aggregation is "next" to a series of buckets
instead of embedded "inside" them. For example, the
max_bucket aggregation uses the
buckets_path to specify
a metric embedded inside a sibling aggregation:
Instead of pathing to a metric,
buckets_path can use a special
"_count" path. This instructs
the pipeline aggregation to use the document count as it’s input. For example, a moving average can be calculated on the document
count of each bucket, instead of a specific metric:
Dealing with dots in agg namesedit
An alternate syntax is supported to cope with aggregations or metrics which
have dots in the name, such as the
percentile. This metric
may be referred to as:
Dealing with gaps in the dataedit
Data in the real world is often noisy and sometimes contains gaps — places where data simply doesn’t exist. This can occur for a variety of reasons, the most common being:
- Documents falling into a bucket do not contain a required field
- There are no documents matching the query for one or more buckets
- The metric being calculated is unable to generate a value, likely because another dependent bucket is missing a value. Some pipeline aggregations have specific requirements that must be met (e.g. a derivative cannot calculate a metric for the first value because there is no previous value, HoltWinters moving average need "warmup" data to begin calculating, etc)
Gap policies are a mechanism to inform the pipeline aggregation about the desired behavior when "gappy" or missing
data is encountered. All pipeline aggregations accept the
gap_policy parameter. There are currently two gap policies
to choose from:
- This option treats missing data as if the bucket does not exist. It will skip the bucket and continue calculating using the next available value.
This option will replace missing values with a zero (
0) and pipeline aggregation computation will proceed as normal.