Currently using ELK stack 8.91.
Fleet enable. Elasticc-agent deployed on around 100 Servers/vm.
I notice that indexes will never be cleared. Seems to be a default behavior.
I need to know how to setup an Index Lifecycle Policies to clean old logs.
Can you let me know how can I setup this ?
You should increase the maxium primary shard size, 10 MB is way too small and not recommended at all. The recommended size for primary shard is something close to 50 GB.
With a primary shard size of 10 MB you risk creating too many indices/shards that can impact your cluster and even block writes if you reach the maximum shards allowed.
Are the backing indices for the Elastic Agent data streams being deleted? If they are being deleted, then I'm not sure what is the issue.
Depending on the integrations you are using Elastic Agente can be very noisy.
So I restore my snaphot VM and adjust my config as follow :
Maximum primary shard size : 50GB
Maximum age : 2 days
Delete phase Move data into phase when: 12 hours
Are the backing indices for the Elastic Agent data streams being deleted?
How can i know this information ?
Space available actually is around 100gb. If needed I can add more, but I want to control space used before.
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.