zalando / zalando/postgres-operator
Add prometheus metrics for postgres operator himself
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? postgres-operator:v1.8.2
- **Where do you run it - cloud or metal? Kubernetes Bare Metal K8s
- Are you running Postgres Operator in production? yes
- Type of issue? feature request
Add prometheus metrics for postgres operator himself
As a Cluster Operator we want to monitoring the operator and no only the databases.
For his we need metrics we can monitoring in grafana/prometheus
There is already a PR https://github.com/zalando/postgres-operator/pull/1529
Background: We want Alerts for Sync Failed and also monitoring how many pg istances the postgres operator is managing
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 reviewing the existing PR at https://github.com/zalando/postgres-operator/pull/1529 and the operator's current metrics behavior. Done means exposing metrics for sync failures and the number of PostgreSQL instances managed by the operator so they can be monitored in Prometheus and Grafana.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql, prometheus
- Domain
- databases, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100