NETWAYS / NETWAYS/ansible-collection-elasticstack
[Bug]: Filebeat system module is enabled whenever any module is defined
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
In the filebeat "Configure modules" block, the "Enable System module" task writes modules.d/system.yml whenever beats_filebeat_modules is defined — regardless of whether "system" is in the list. Enabling e.g. only "nginx" therefore also enables the system module unintentionally.
Fix: only write/enable the system module when it is actually requested.
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 in the Filebeat "Configure modules" block, focusing on the "Enable System module" task and its modules.d/system.yml target. Reproduce with beats_filebeat_modules containing only nginx, then verify that system.yml is not written or enabled; confirm it still is when system is requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100