prometheus-community / prometheus-community/postgres_exporter
pg_stat_user_tables collector only scraped targets in postgres
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 835
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 10
Description
pg_stat_user_tables collector only scaped targets in the database of postgres, but actually in a dev or product database system, we have more databases and schemas , it should scrapd all targers in other databases and schemas in it's own namespaces, the database names self-defined or autodiscoveryed.
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 locating the pg_stat_user_tables collector and reviewing how it selects databases and schemas. Confirm the expected behavior for self-defined and autodiscovered database names, then verify that metrics are collected from relevant databases and schemas beyond postgres.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql, prometheus
- Domain
- databases, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100