Identify useful metrics to be exported from the webhook controller
Open
Nobody has claimed this yet.
kind/misc
- Dominant language
- Go
- Stars
- 6
- Forks
- 19
- Avg merge
- 12h 36m
- Merged PRs (30d)
- 27
Description
Assess additional metrics required for pruner webhook and include service monitor in Operator as applicable
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 reading the webhook controller and the existing metrics setup to identify what the pruner webhook currently exports. Determine which additional metrics are useful, then inspect the Operator configuration for ServiceMonitor support. The work is done when the selected metrics are exported and the ServiceMonitor is included if applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100