NETWAYS / NETWAYS/ansible-collection-elasticstack
Filebeat: Config loading
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
Hi,
you should remove filebeat input configuration from the service YAML filebeat.yml.j2 and start working multiple YAML config files from subdirectory like:
filebeat.config.inputs:
enabled: true
path: inputs.d/*.yml
From there you can load the different input configurations for e.g. TCP or UDP. You could also then introduces tags which roll out different kind of input types on your hosts
This keeps the main configuration in filebeat.yml thin and better to read.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the service YAML template filebeat.yml.j2 and reviewing how its current input configuration is rendered. Move toward the requested inputs.d/*.yml structure, with separate TCP or UDP input configurations and host-specific tags, then verify that the main filebeat.yml remains thin and the configurations load correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100