In packetbeat.yml I used to have this configuration to map all indices to my default ilm policy:
setup:
ilm:
enabled: auto
overwrite: true
policy_name: default-metric-beats-ilm
Actually this was working but after upgrading to 7.6.1 the new indices of packetbeat (and my other beats) are no more linked to this policy.
Has there something changed. Do I need to set this differently now?
cc: @elastic/beats
@ChrsMark Is this ah known bug If I may ask? If yes, is there a workaround?
Pinging @elastic/integrations (Team:Integrations)
Not sure @phlegx . This will require investigation.
Hello again. May I ask if somebody had some time to look at this issue?
Hey @phlegx I was not able to reproduce it with 7.6.2.
Using:
setup.ilm:
enabled: auto
overwrite: true
policy_name: default-metric-beats-ilm-42-test
Running:
./metricbeat -e -d "*" setup
Then going to Kibana Index Management page and here what I see:

So I guess that it works on my end? I use 7.6.2 for the whole stack (es, kibana, beats)
Let me know if that helps.
Hi @ChrsMark thanks for testing things out. I just upgraded to version 7.6.2 and now with that version it seems to work for me again. I'm not totally sure what has caused this, since the upgrade process and the configs are all the same.
Nice @phlegx !
Just to let you know that for stuff like that we have a policy to first open an issue in https://discuss.elastic.co/c/beats/metricbeat and only if it is a confirmed bug to transfer the issue here in GH. We use this approach to escalate issues better and for better community support.
Best!