zalando / zalando/postgres-operator
Operators metrics
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
- Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.10.0
- Where do you run it - Bare Metal K8s
- Are you running Postgres Operator in production? no
- Type of issue? feature request
Hi,
I didn't find in documentation anything about operator metrics( self metrics).
We use operator for review stages and operator, every day, deploy and destroy 100-200 Postgres clusters, but we can't monitor operations status.
Could you have plans about add self metrics( clusters count\stats\status\etc) and default go metrics via prometheus exporter?
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 or tests; start by reviewing the operator's existing metrics exposure and Prometheus integration. Clarify which cluster counts, statistics, and statuses are required, then consider the work complete when the requested self-metrics and default Go metrics are exposed in a Prometheus-compatible form and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql, prometheus
- Domain
- databases, infrastructure, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100