zalando-incubator / zalando-incubator/stackset-controller
Collect more metrics for monitoring and alerting
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 183
- Forks
- 29
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 5
Description
The prometheus endpoint should expose more metrics that allow to detect whether stackset controller is running well.
Some possibilities:
- number of errors / error rate
- number of stacksets / stacks under control
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 Prometheus endpoint and the stackset controller's existing metrics instrumentation. Define the required metrics and their labels from the controller's error handling and managed stackset/stack counts; done means the endpoint exposes useful signals for controller health, including errors and resources under control.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, prometheus
- Domain
- infrastructure, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100