Optimize output from grafana alerts
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
There is a huge amount of info being dumped into both the legacy alerts and the new ones added recently for pods and nodes. We need to do some trimming to make sure the necessary information is front and center and easily digested.
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
The issue does not name files, tests, or entry points. Start by locating the legacy Grafana alerts and the newer pod and node alert definitions, then compare which fields are emitted. Done means the alerts retain necessary information while presenting it in a more focused, easily digestible order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana
- Domain
- observability
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100