I am seeing an issue on the ELK production server w.r.t to ILM.
We have a production server (standalone) where ELK stack is installed and has the version 7.17.15.
Recently ILM policy was implemented and is running successfully. Please find the details below.
# filebeat version
filebeat version 7.17.15 (arm64), libbeat 7.17.15 [b474d2803ed2961f23f614d7213d9099fb0b4354 built 2023-11-08 19:08:34 +0000 UTC]
GET _ilm/status
{
"operation_mode" : "RUNNING"
}
However, currently I am seeing the filebeat indexes of different versions from other client servers and are utilizing high disk space e.g. as below.
yellow open filebeat-8.11.1 J9GUiOhkThilgzBp0i0RPQ 1 1 399800458 0 182.8gb 182.8gb
yellow open filebeat-8.11.2 hp8zHe1hTKmfuAJnTsy5fg 1 1 39897815 0 12.9gb 12.9gb
yellow open filebeat-8.10.4 HbQfL0pGS_ClJLLBWGFYUQ 1 1 4042769 0 920.3mb 920.3mb
I tried to look for a solution from forums and other sources but I could not find the right one. Please need to know on how to fix this issue and is there a way out, if we can assign to the existing ILM policy runnning (for beat 7.17.15) and also it should not conflict with the existing ILM policy because of the filebeat versions on the main ELK server and others from the client servers.
I have tried reading from other sources and I am still not able to come to the conclusion on how to fix the current issue. could someone please help with their inputs?
Thanks for the reply on this post. Please find the details mentioned inline.
As per my analysis these indices are coming from the other hosts.
Yes, I want to apply ILM for these indices. More details on the such indices with size is share below.
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
yellow open filebeat-8.11.1 neEszcRuQ3WFEdk_lZw7Ng 1 1 233861425 0 107.7gb 107.7gb
yellow open filebeat-8.11.2 ytS9uDDvQDSeoLCtinUNFQ 1 1 22845860 0 7.3gb 7.3gb
yellow open filebeat-8.10.4 HbQfL0pGS_ClJLLBWGFYUQ 1 1 6129880 0 1.3gb 1.3gb
yellow open filebeat-8.10.4-2024.01.12 7ah5nAK6ShSf8oQhCSar3w 1 1 51352 0 10.2mb 10.2mb
Yes, can have separate ILM policy created for filebeat version 8.x? or its possible to add these to the existing ILM which in place?
ILM implemented for filebeat on the master ELK (stand alone) and the filebeat version is 7.17.15 and ILM is in operation mode successfully.
# filebeat version
filebeat version 7.17.15 (arm64), libbeat 7.17.15 [b474d2803ed2961f23f614d7213d9099fb0b4354 built 2023-11-08 19:08:34 +0000 UTC]
GET _ilm/status
{
"operation_mode" : "RUNNING"
}
I am trying to check if there's a way to that these filebeat indices for version 8.x can be added to the existing ILM policy or we have to separate and create a new ILM policy.
Since its 8.x, it may work differently as per my earlier understanding.
Question: Also, do you have something like logstash in between filebeat and elasticsearch?
Ravi: Yes, we do have a logstash in between filebeat and elasticsearch
What ILM policy are you trying to apply?
Ravi: Same as what is in place for filebeat (7.x) currently.
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.