Open Nandeeshbb opened 4 months ago
This issue doesn't have a Team:<team>
label.
@Nandeeshbb Hi! This is more related to add_kubernetes_metadata
processor.
If I'm not wrong, this wouldn't create a new index in ElasticSearch but a new index (i.e. identifier) in local memory cache. The concept of index
in terms of add_kubernetes_metadata
can be found here.
The logs Created index xxx
means that it has internally created an index which will be used to extract kubernetes pod metadata.
Thanks @VihasMakwana ,,but I have followed the same , but not able to create index per pod name .. Do you have any idea?
Any help here?
Please help on this and stuck in this from last 5 days and not able to create index for each pod in elastic search using filebeat.
Elastic search version: 7.10.1 AWS Filebeat version: 7.12.1
Filebeat configuration file:
Help would be very much appreciated..
And the file beat logs says index is created but dont see any index with name of the pod