You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the APM app, we are currently using value_count aggregations for transactions, as transaction metric documents use histogram fields, meaning doc_count is no longer representative. ES now also has a _doc_count data type that allows us to specify how many documents a transaction metric document represents. ES will then use this field in its bucketing aggregations, removing the need for an additional value_count aggregation, which should speed up some of our queries and remove some complexity from our queries.
I think this should be straightforward. I thought we would need to update betas and fields.yml; that is not the case.
To whomever implements this: I think we'll just need to add a field describing the doc count to model.Metricset, and use that to add a _doc_count field to the metric event docs that we index.
In the APM app, we are currently using
value_count
aggregations for transactions, as transaction metric documents use histogram fields, meaningdoc_count
is no longer representative. ES now also has a_doc_count
data type that allows us to specify how many documents a transaction metric document represents. ES will then use this field in its bucketing aggregations, removing the need for an additionalvalue_count
aggregation, which should speed up some of our queries and remove some complexity from our queries.https://www.elastic.co/guide/en/elasticsearch/reference/master/mapping-doc-count-field.html
The text was updated successfully, but these errors were encountered: