NETWAYS / NETWAYS/ansible-collection-elasticstack
Add solution for multiple retention times
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
We often have to split logs into several retention categories. The usual way is to use different indices/ILM policies/data streams for types of logs.
We should have a way of splitting logs by condition (like in Redis outputs in pipeline management). I don't know if there's a solution with Elasticseach-pipelines but we can definitely have it in our Elasticsearch outputs in Logstash. If both works, why not implement both?
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 how Elasticsearch outputs and Logstash pipeline management currently handle index selection and retention policies. Clarify whether the change should support conditional routing in Elasticsearch outputs, Elasticsearch pipelines, or both. Done should mean logs can be split into multiple retention categories by condition, with the supported scope and behavior documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch
- Domain
- data, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100