prometheus-community / prometheus-community/postgres_exporter
respond with non-200 (path "/") when errors were returned from database.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 835
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 10
Description
Proposal
Respond to clients with non-200 at root path ("/", or "/healthz") when errors are returned from database due to login.
Background
Postgres_exporter doesn't really have a healthcheck path to be used in liveness,readiness checks; simply the fact that the webserver is running is good enough for readiness, but not liveness.
Use Case
For users incorporating Vault for database authentication, credentials may be revoked at any time. When this happens, or if credentials are renewed, the postgres_exporter currently has no way of indicating this to clients.
Contributor guide
No contributing guide indexed for this repository
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 tracing the root (/) and /healthz entry points and the database login error path in postgres_exporter. Done means clients receive a non-200 response at the health endpoint when database authentication fails, including failures caused by revoked or renewed credentials.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- api, backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100