I’m currently monitoring ELK stack through metricbeat (Elasticsearch, Kibana & Logstash)
but the monitoring index for Elasticsearch “.ds-.monitoring-es…….” is around 15GB per day so I switched the period to 60 seconds instead of 10, but I think the size of the index is way to big compared to the data provided.
So my question is, how do I limit the info monitored by Metricbeat without losing essential data?
I tried to inspect the index and found out that most of the fields are empty.
Could you please share the number of nodes in your cluster for which this monitoring is enabled along with 1 of the dummy <metricbeat.yml > as to see what all modules as enabled.
Also share the output for below query via devtools :
GET _cat/indices/.ds-.monitoring-es*?v&s=store.size:desc
GET _cat/indices/.ds-.monitoring-es*?v&s=store.size:desc :
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size dataset.size
green open .ds-.monitoring-es-8-mb-2025.08.19-000197 dO4fIXr8TsGBlygeNEN4fg 1 0 24154649 0 14.9gb 14.9gb 14.9gb
green open .ds-.monitoring-es-8-mb-2025.08.20-000199 aByXutjDTFO5OuykEsSt7g 1 0 5169566 0 3.1gb 3.1gb 3.1gb
.ds-.monitoring-es-8-mb-2025.08.20-000199 is much smaller because the period is set to 60s
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.