zalando / zalando/postgres-operator
Expose operator metrics (prometheus)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
It would be great to have a prometheus metrics endpoint available in postgres-operator to be able add monitoring at the operator level (not the DBs themselves). An example would be when the operator fails to sync a DB for whatever reason. Currently I don't see a way to be notified about these events except parsing the operator's logs.
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
No files, tests, or entry points are named. Start by locating the operator's sync and error-handling paths and any existing HTTP or metrics setup; define the endpoint and the operator-level events it must expose, then verify that sync failures can be monitored without parsing logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, prometheus
- Domain
- infrastructure, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100