NETWAYS / NETWAYS/ansible-collection-elasticstack
Allow for other TCP and UDP inputs
Open
Nobody has claimed this yet.
component:filebeat
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
While the current ones with a fixed port number are great for easy starts, we should provide a way to add more and better customizable tcp and udp inputs.
note: That's a whole new feature, don't just change the existing ones.
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
Review the existing fixed-port TCP and UDP input definitions in the Ansible collection and compare how they are configured. Before implementation, clarify which customizable inputs and options are required, then define completion criteria for adding new inputs without changing the existing ones.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100