I'm using an on-prem version of Elasticsearch in a GCP instance, and I'm having to deal with the huge amounts of data quickly accumulating into my instance's storage. Especially Metricbeat data, that is far to extensive and detailed. We decided on using the Rollup Jobs feature in Elasticsearch and …

Well now that I understand the rollup feature better, i found out that: You save terms query by marking the '.keyword' field instead of the field itself Histogram fields make the rollup huge and mess up the timestamp (we lose the date field so we can't do much with the data), so you should only sa…

"The field [metricset.name] must be aggregatable across all indices" and a huge rolled-up index

Elastic Stack Elasticsearch

system (system) Closed February 21, 2020, 9:01pm 3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Unable to run the default rollup job Elasticsearch	1	365	June 30, 2020
Rollup job failed to find field Elasticsearch	4	1522	September 19, 2018
Rollup index Elasticsearch	2	1490	April 22, 2019
Rollup Jobs and Limitations / Data Types Elasticsearch	3	410	August 24, 2020
Can an Elasticsearch rollup job dynamically create indexes like Logstash does? Elasticsearch	14	2224	October 1, 2018

"The field [metricset.name] must be aggregatable across all indices" and a huge rolled-up index

Related topics