deckhouse / deckhouse/deckhouse
[monitoring] Add labels to the kubectl get clusteralerts -owide output
Open
Nobody has claimed this yet.
area/ux
priority/backlog
source/deckhouse-team
type/enhancement
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 162
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 653
Description
Preflight Checklist
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for an issue that matches the one I want to file, without success.
Use case. Why is this important?
This will allow to use a simple grep to search for the right alerts.
Proposed Solution
Added output .alert.labels
Additional Information
No response
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 implementation and tests for the kubectl get clusteralerts -owide output, then inspect how alert fields are selected for wide output. Add the alert labels to that output and verify that users can grep the rendered labels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100