[Feature]: Unify default Beats output to elasticsearch

Open Beginner friendly
#519 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
elasticsearch
Domain
devops

Research direction

Start by locating the definitions and defaults for beats_filebeat_output, beats_auditbeat_output, and beats_metricbeat_output in the Ansible collection. Compare the related data-driven Beats work in issues #510, #505, and #516, then verify that all three defaults are elasticsearch and that the breaking-change behavior is documented or covered by the relevant checks.

Written by the indexing model from the issue text.

Description

component:beats

beats_filebeat_output defaults to logstash, but beats_auditbeat_output / beats_metricbeat_output default to elasticsearch — inconsistent.

Make all three default to elasticsearch. Breaking: setups relying on Filebeat → Logstash by default must then set beats_filebeat_output: logstash explicitly.

Pairs with the data-driven Beats work (#510 / #505 / #516).

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.