I have 11 elasticsearch nodes 3 master node 6 data node and 2 coordinate node.We are running latest version of elasticsearch 7.13.2
we have installed metricbeat and configured in all elasticsearch node we are monitoring our ELK stack and we have observed that .monitoring-es-* indices has 200gb ,100,150gb and .monitoring-logstash-* has less amount of data size same with the kibana
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open .monitoring-es-7-mb-2021.07.04 cZ0Rq2QSTsWaSVkYbUqCcA 1 1 93685117 0 135.4gb 67.7gb
green open .monitoring-es-7-mb-2021.07.05 soF59jJFTYqxUHagyxAH3g 1 1 94039120 0 137.5gb 68.7gb
green open .monitoring-es-7-mb-2021.07.06 7C9h4JdiSqqArvIq_KRmMQ 1 1 88497612 0 126.9gb 63.4gb
green open .monitoring-es-7-mb-2021.07.07 Z7Q53VgKSnm50Co1mOgPrw 1 1 26045340 0 39.4gb 20.8gb
green open .monitoring-es-7-mb-2021.07.01 34OMsmgVRruMjq5-E0UqXQ 1 1 91449387 0 133gb 66.5gb
green open .monitoring-es-7-mb-2021.07.02 TD848mdHRxSPzr9rL8p8ow 1 1 92942331 0 134.9gb 67.4gb
green open .monitoring-es-7-mb-2021.07.03 Jy4pGaFvQUyuwtGdYfDE-w 1 1 93367837 0 135.2gb 67.6gb
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open .monitoring-logstash-7-mb-2021.07.07 aP4IvdvQQmWGqCxMk96nYg 1 1 1471408 0 164.9mb 82.5mb
green open .monitoring-logstash-7-mb-2021.07.05 _ahnIYIRTbihc5gGC_-7Wg 1 1 5819446 0 690.3mb 345.5mb
green open .monitoring-logstash-7-mb-2021.07.06 YPNxCJKjRByDTMC9HdbYOg 1 1 5271822 0 594.4mb 297mb
green open .monitoring-logstash-7-mb-2021.07.03 i66BsXz6SvmUFT0fP14E-Q 1 1 5806084 0 680.6mb 340.7mb
green open .monitoring-logstash-7-mb-2021.07.04 y6WR6VAnTuanZXCUaOxB0A 1 1 5806084 0 680.3mb 341.2mb
green open .monitoring-logstash-7-mb-2021.07.01 XHzk_U6XSuK2QCNMVfiQhA 1 1 5806084 0 682.4mb 340.4mb
green open .monitoring-logstash-7-mb-2021.07.02 gUtSibBZTCaHIxTLmt2xJw 1 1 5806084 0 685.1mb 342mb
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open .monitoring-kibana-7-mb-2021.07.06 JiQhlpMnT32mSBcezPPEvA 1 1 16410 0 6.9mb 3.4mb
green open .monitoring-kibana-7-mb-2021.07.07 Cs8bWPEXT_Op-86Iw1p9dw 1 1 4408 0 2mb 1mb
green open .monitoring-kibana-7-mb-2021.07.01 -_styBN1R3ybRkUZnkUapw 1 1 17280 0 6.8mb 3.4mb
green open .monitoring-kibana-7-mb-2021.07.04 HWKDJECvRYWCZj5JljKqPA 1 1 17280 0 6.7mb 3.4mb
green open .monitoring-kibana-7-mb-2021.07.05 -LFY0z1qQEmTDZJ8KnSFUA 1 1 17280 0 7.1mb 3.5mb
green open .monitoring-kibana-7-mb-2021.07.02 mIf16DvcRKGkdmcLfpWkuw 1 1 17280 0 6.9mb 3.4mb
green open .monitoring-kibana-7-mb-2021.07.03 rpWPBe3oRrSnam1_NpumIw 1 1 17280 0 6.7mb 3.3mb
we have enable elasticsearch-xpack module in metricbeat
elasticsearch-xpack.yml
# Module: elasticsearch
# Docs: https://www.elastic.co/guide/en/beats/metricbeat/7.10/metricbeat-module-elasticsearch.html
- module: elasticsearch
xpack.enabled: true
period: 10s
metricsets:
- cluster_stats
- index
- index_recovery
- index_summary
- node
- node_stats
- pending_tasks
- shard
hosts:
- "https://xx.xx.xx.xx:9200" #em1
- "https://xx.xx.xx.xx:9200" #em2
- "https://xx.xx.xx.xx:9200" #em3
- "https://xx.xx.xx.xx:9200" #ec1
- "https://xx.xx.xx.xx:9200" #ec2
- "https://xx.xx.xx.xx:9200" #ed1
- "https://xx.xx.xx.xx:9200" #ed2
- "https://xx.xx.xx.xx:9200" #ed3
- "https://xx.xx.xx.xx:9200" #ed4
- "https://xx.xx.xx.xx:9200" #ed5
- "https://xx.xx.xx.xx:9200" #ed6
scope: cluster
ssl.certificate_authorities: ["/etc/elasticsearch/certs/ca/ca.crt"]
username: "xxxx"
password: "********"
Is there any way to control .monitoring-es index