elasticsearch/docs/reference/aggregations/metrics/valuecount-aggregation.asciidoc
Nik Everett 6a1220e7f3
Convert metric aggs docs runtime fields (#71260)
This replaces the `script` docs for bucket aggregations with runtime
fields. We expect runtime fields to be nicer to work with because you
can also fetch them or filter on them. We expect them to be faster
because their don't need this sort of `instanceof` tree:
a92a647b9f/server/src/main/java/org/elasticsearch/search/aggregations/support/values/ScriptDoubleValues.java (L42)

Relates to #69291

Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
Co-authored-by: Adam Locke <adam.locke@elastic.co>
2021-04-05 13:08:13 -04:00

140 lines
3.5 KiB
Text

[[search-aggregations-metrics-valuecount-aggregation]]
=== Value count aggregation
++++
<titleabbrev>Value count</titleabbrev>
++++
A `single-value` metrics aggregation that counts the number of values that are extracted from the aggregated documents.
These values can be extracted either from specific fields in the documents, or be generated by a provided script. Typically,
this aggregator will be used in conjunction with other single-value aggregations. For example, when computing the `avg`
one might be interested in the number of values the average is computed over.
`value_count` does not de-duplicate values, so even if a field has duplicates each value will be counted individually.
[source,console]
--------------------------------------------------
POST /sales/_search?size=0
{
"aggs" : {
"types_count" : { "value_count" : { "field" : "type" } }
}
}
--------------------------------------------------
// TEST[setup:sales]
Response:
[source,console-result]
--------------------------------------------------
{
...
"aggregations": {
"types_count": {
"value": 7
}
}
}
--------------------------------------------------
// TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
The name of the aggregation (`types_count` above) also serves as the key by which the aggregation result can be
retrieved from the returned response.
==== Script
If you need to count something more complex than the values in a single field
you should run the aggregation on a <<runtime,runtime field>>.
[source,console]
----
POST /sales/_search
{
"size": 0,
"runtime_mappings": {
"tags": {
"type": "keyword",
"script": """
emit(doc['type'].value);
if (doc['promoted'].value) {
emit('hot');
}
"""
}
},
"aggs": {
"tags_count": {
"value_count": {
"field": "tags"
}
}
}
}
----
// TEST[setup:sales]
// TEST[s/_search/_search?filter_path=aggregations/]
////
[source,console-result]
----
{
"aggregations": {
"tags_count": {
"value": 12
}
}
}
----
////
[[search-aggregations-metrics-valuecount-aggregation-histogram-fields]]
==== Histogram fields
When the `value_count` aggregation is computed on <<histogram,histogram fields>>, the result of the aggregation is the sum of all numbers
in the `counts` array of the histogram.
For example, for the following index that stores pre-aggregated histograms with latency metrics for different networks:
[source,console]
--------------------------------------------------
PUT metrics_index/_doc/1
{
"network.name" : "net-1",
"latency_histo" : {
"values" : [0.1, 0.2, 0.3, 0.4, 0.5],
"counts" : [3, 7, 23, 12, 6] <1>
}
}
PUT metrics_index/_doc/2
{
"network.name" : "net-2",
"latency_histo" : {
"values" : [0.1, 0.2, 0.3, 0.4, 0.5],
"counts" : [8, 17, 8, 7, 6] <1>
}
}
POST /metrics_index/_search?size=0
{
"aggs": {
"total_requests": {
"value_count": { "field": "latency_histo" }
}
}
}
--------------------------------------------------
For each histogram field the `value_count` aggregation will sum all numbers in the `counts` array <1>.
Eventually, it will add all values for all histograms and return the following result:
[source,console-result]
--------------------------------------------------
{
...
"aggregations": {
"total_requests": {
"value": 97
}
}
}
--------------------------------------------------
// TESTRESPONSE[skip:test not setup]