prometheus-community / prometheus-community/postgres_exporter
Not able to run multiple instances of exporter (Multiple postgres instances)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 835
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 10
Description
When I run docker version of postgres exporter, I can access the the localhost:9187, but when I have requirement of pulling metrics from mutilple postgres instances with certificates. when I run on same port, I get issue running another exporter. If I run exporter on other machin, I can not add them to prometheus due port conflict. How do proceed further, any suggestion?
docker run -p 9187:9187 -v /certs:/etc/ssl/certs/ -e DATA_SOURCE_NAME="postgresql://postgres:password@xx.xx.xxx.xxx:5432/postgres?sslmode=verify-ca&sslrootcert=/etc/ssl/certs/ss.pem&sslcert=/etc/ssl/certs/cc.pem&sslkey=/etc/ssl/certs/ck.pem" prometheuscommunity/postgres-exporter
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
The issue provides only a Docker invocation using DATA_SOURCE_NAME and port 9187; it names no repository files, tests, or entry points. Begin by reading the exporter documentation and configuration handling for multiple PostgreSQL targets, then determine whether a documented setup or a product change is needed and define completion accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, postgresql, prometheus
- Domain
- databases, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100