Open linuxmanju opened 1 year ago
The only scenario that should throw a 500 on the /probe endpoint is if we fail to create the collector. In that case, the error should be in the response body. Can you query the probe URL and see what the output is?
I opened #918 to also log this error.
What did you do?
Configured latest stable release of postgres_exporter, Created an auth module.
Promtheus scrape job
What did you expect to see?
Scrape to happen successfully with metrics being available in prometheus.
What did you see instead? Under which circumstances?
Environment
prod
Linux 5.10.0-23-cloud-amd64 x86_64
postgres_exporter version:
postgres_exporter, version 0.13.2 (branch: HEAD, revision: 8c3604b85e38ae7141e84ecdc318b6015a196c97) build user: root@2ea2be721819 build date: 20230724-00:08:19 go version: go1.20.6 platform: linux/amd64 tags: netgo static_build
postgres_exporter flags:
14.0