elastic / elastic/beats

setup.ilm.overwrite configuration don't work.

Open
#44,702 2 comments 0 reactions 0 assignees View on GitHub
needs_team Stalled
Dominant language
Go
Stars
12.7k
Forks
5k
Avg merge
2d 54m
Merged PRs (30d)
381

Description

I use filebeat image(7.17) as a sidecar container in my k8s cluster,i found the setup.ilm.overwrite configuration don't work.After I modify setup.ilm.policy_name and restart the container, the index's lifecycle policy in kibana didn't change.

filebeat.yml be like :
filebeat.config:
modules:
path: ${path.config}/modules.d/*.yml
reload.enabled: false

filebeat.inputs:

- type: filestream
id: ${FS_ID}
enabled: true
paths:
- ${YOUR_LOG_PATH}

setup.template.settings:
index.number_of_shards: 1

setup.template.enabled: true
setup.ilm.enabled: true
setup.ilm.policy_name: ${ILM_POLICY_NAME}
setup.ilm.rollover_alias: ${ES_INDEX}
setup.ilm.overwrite: true
setup.template.name: ${ES_INDEX}
setup.template.pattern: "${ES_INDEX}-*"
processors:
- drop_fields:
fields: ["_source","_type","_id","_index","agent","cloud","log","ecs","log_type","input_type","offset","beat","source","type","input","host"]

output.elasticsearch:
hosts: ${ES_CLUSTER} #cluster array
index: ${ES_INDEX} #app-template
username: 'elastic'
password: 'xxxx'
ssl.enabled: true
ssl.certificate: "/usr/share/filebeat/cert.pem"
ssl.key: "/usr/share/filebeat/key.pem"
ssl.certificateAuthorities: ["/usr/share/filebeat/ca.pem"]

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.