Be intentional about log retention
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Set log retention on eks cloudwatch log groups: Appears there is no retention policy on the control room log group for the eks cluster. The prod one is at 99gb or so, it's not massive but we should set a retention on it. I didn't check the rest, stage prob bigger.
Also look at loki storage and retention
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 EKS CloudWatch log group configuration and the Loki storage and retention configuration. Check the production and staging log groups, then verify that the intended retention policies are applied to the EKS and Loki logs without leaving the large groups unbounded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100