prometheus-community / prometheus-community/postgres_exporter
should add connection time cost
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 835
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 10
Description
in new versions , we can find the prometheus targets like collector="bgwriter" ,collector="bgwriter" collector="database", but no collector="connection", we should add a connection target to tell us if this is a connection issue, second one , [0.13.0] versions
extend.query-path features was deprecated , but we really need this features , is the PG_EXPORTER_EXTEND_QUERY_PATH still working?
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 in the postgres_exporter repository by tracing how Prometheus collector targets are defined and how PG_EXPORTER_EXTEND_QUERY_PATH is handled. Confirm whether the requested connection target and the deprecated extend.query-path behavior are separate changes, then verify that the exporter exposes the connection metric and documents or preserves the expected configuration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql, prometheus
- Domain
- databases, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100