prometheus-community / prometheus-community/postgres_exporter
Multi-target (BETA) does not support passwordless users
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 835
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 10
Description
I am trying out the new beta release v0.12.0-rc.0 on Linux (thank you all so much for working on this feature!!). I got it all working correctly, except for the user I have been monitoring with does not have a password, so when I configure using this account I get an error on scrape saying, "auth_module {my_module_name} has no username or password". I somewhat got around this by providing a bogus password, but using that method I do not get all of the metrics I expect (by comparing the current working version of the exporter). Both collectors (bgwriter and database) both return success (or 1), but the probe_success returns 0.
Are there any thoughts or concerns around supporting passwordless user accounts? My use case could be different than what was intended, and also I completely understand this is a brand new release so things will get worked out. I just wanted to throw this out there so someone else could see what I'm seeing.
Thanks again for your hard work everyone!!
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 reproducing the multi-target (BETA) scrape with a passwordless PostgreSQL user on Linux using the v0.12.0-rc.0 configuration described in the report. Trace the authentication and scrape results, then verify that passwordless users expose the expected metrics and that probe_success reports success.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- databases, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100