Aggregate logs for app replicas
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
If you have a Deployment with many replicas, it can get a bit weird when they're all logging right to the Logs tab. It would be nice to have more fine-grained controls over how these things are aggregated (e.g., "prefix with pod name", "aggregate by pod name into windows of x seconds and report contiguously").
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 tracing how Deployment replica logs reach the Logs tab and identify the existing aggregation behavior. Clarify which controls are required, including pod-name prefixes or time-windowed aggregation, then define expected output and tests for each mode before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100