prometheus-community / prometheus-community/postgres_exporter
The mixin dashboard uses metrics that don't exist
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 835
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 10
Description
What did you do?
Run 0.13.2 in Kubernetes as a sidecar container via the postgres-operator.
Load this dashboard: https://github.com/prometheus-community/postgres_exporter/blob/master/postgres_mixin/dashboards/postgres-overview.json
What did you expect to see?
Something I could further tweak.
What did you see instead? Under which circumstances?
It appears all or nearly all the metrics this dashboard is looking for don't exist or are not being exported. - There are potentially similar ones being exported, but I might as well be starting from scratch because I can't know for sure if for example pg_stat_database_conflicts_confl_deadlock should replace pg_stat_database_deadlocks or what.
Environment
-
System information:
Linux 5.10.104-linuxkit x86_64 -
postgres_exporter version:
quay.io/prometheuscommunity/postgres-exporter:v0.13.2 -
postgres_exporter flags:
--log.level=warn
--log.format=json
-
PostgreSQL version:
12,13,14
-
Logs:
no error logs
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 postgres_mixin/dashboards/postgres-overview.json and compare every referenced metric with the metrics exported by postgres_exporter for PostgreSQL 12, 13, and 14. Determine the correct metric names and update the dashboard so its panels use metrics that are actually exported and display data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql, prometheus
- Domain
- databases, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100