Beats: Metricbeat Doesn't Get ILM Policy via Auto ILM

[dsanders11]

• Version: 7.0.1
• Operating System: CentOS 7.4

Logs

idxmgmt/std.go:165  Set output.elasticsearch.index to 'metricbeat-7.0.1' as ILM is enabled.
idxmgmt/std.go:361  Set setup.template.name to '{metricbeat-7.0.1 {now/d}-000001}' as ILM is enabled.
idxmgmt/std.go:366  Set setup.template.pattern to 'metricbeat-7.0.1-*' as ILM is enabled.

Can anyone spot the problem? The template pattern won't match the index name, so the index gets created without the template applying, so ILM doesn't actually apply.

[ph]

@dsanders11 Can you share your metricbeat configuration?

[dsanders11]

@ph, it was the standard configuration on CentOS 7.4. All I changed was the cloud.id and cloud.auth settings.

[webjunkie]

I figured out I have the same problem. Default config, no special index names set. ILM seems to be enabled automatically and the template seems not to be used because of the pattern mismatch.

[CodeAdminDe]

The problem seems to exist.
At a fresh cluster (kibana 7.8.0, elasticsearch 7.8.0 with metricbeat 7.8.0) after inital import of index_template, ilm-policy, index-pattern and dashboards via metricbeat setup command.

At first run of metricbeat to collect data, an index will be created (index: metricbeat-7.8.0) but the template (index patterns: metricbeat-7.8.0-*) won't be applied.
It was noticed because no rollover index was created and because of this, the ILM Policy was not applied to the index.
Manual application of ILM Policy to the metricbeat-7.8.0 index failed, of course.

Adjusting the template index pattern after creation (before first data collection) seems to be a workaround. But is that a good idea, or does it trigger not yet known problems?