NETWAYS / NETWAYS/ansible-collection-elasticstack
[Feature]: Tcp and Udp input of filebeat only accepts global fields
Open
Nobody has claimed this yet.
component:filebeat
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
Describe the feature request
We allow global and local fields for log file inputs in Filebeat. But tcp and udp input only allow global fields. For a customer project we need to be able to set fields also on tcp and udp inputs.
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 collection's Filebeat configuration for TCP and UDP inputs and compare it with the log file input handling described in the issue. Verify how global and local fields are represented, then confirm that TCP and UDP inputs accept local fields in the generated configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, elasticsearch
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100