prometheus-community / prometheus-community/postgres_exporter
pg_up != 1 doesn't work when I stopping PostgreSQL
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 835
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 10
Description
pg_up != 1 alert doesn't work when I stopping PostgreSQL, I think it's happens because when PostgreSQL is down postgres_exporter can't connect to DB.
is this the expected behavior for this exporter and this metric or I did something wrong?
thanks!
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 with the pg_up metric and reproduce the behavior while stopping PostgreSQL, checking whether postgres_exporter can expose a value when it cannot connect. Clarify whether pg_up != 1 is expected to alert in this state; done requires an agreed behavior and corresponding implementation or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql, prometheus
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100