zalando / zalando/postgres-operator
add monitoring
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
what does zalando do for postgres monitoring with any databases run via this operator?
I was thinking of building https://github.com/wrouesnel/postgres_exporter into the database container and having that be monitored via our prometheus operator.
is there any existing plans to add monitoring directly into this project in some way? if not, is there a need for a more detailed discussion/approach prior to contribution or shall I do as the contribution guidelines say and just hack away and send a PR?
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 contribution guidelines, the database container used by the operator, and how the Prometheus operator would consume postgres_exporter metrics. Clarify whether monitoring belongs in this project and define the integration approach before implementation; done means an agreed scope and a contribution plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, postgresql, prometheus
- Domain
- databases, infrastructure, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100