NETWAYS / NETWAYS/ansible-collection-elasticstack
[Feature]: elasticsearch: log4j configuration
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
Describe the feature request
I think the log4j configuration of elasticsearch nodes are missing.
For Logstash nodes its done. (https://github.com/NETWAYS/ansible-collection-elasticstack/blob/99c3884a4455ee155651133abf762f84a2273459/roles/logstash/tasks/main.yml#L145)
Problem is that the default retention is on folder size (2G).
So in Our case we have files back to 2023 in the log folder.
Please add log4j configuration like for logstash.
Thanks in advance
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 with the referenced roles/logstash/tasks/main.yml around line 145, then locate the Elasticsearch role's task and configuration files. Compare how Logstash configures log4j and determine where the equivalent Elasticsearch configuration belongs. Done means Elasticsearch nodes receive log4j retention settings rather than relying only on the default folder-size limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, elasticsearch
- Domain
- devops, observability-sre
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100