[Bug]: Filebeat system module is enabled whenever any module is defined

Open Beginner friendly
#509 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
ansible
Domain
devops

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.

Description

component:filebeat

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.

Dominant language
Jinja
Stars
14
Forks
11
Avg merge
1d 47m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NETWAYS/ansible-collection-elasticstack

All issues in NETWAYS/ansible-collection-elasticstack

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.