Joe Adams

Are you sure that when you exported the key, you used the value of the key and not the name as you show in your comment?

https://github.com/prometheus-community/elasticsearch_exporter?tab=readme-ov-file#elasticsearch-7x-security-privileges

@tac-emil-andresen I don't have sponsorship set up and I'm not sure it's worth it for me. If you want to donate, this is currently my charity of choice: https://www.thefarmette.org/donate Thanks

I need the explanation of the CROSS JOIN before I am willing to merge this code. It's not obvious why it is there so I feel that it deserves some...

If you're asking about the fact that the base branch is out of date, you can reference the github guide here: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch#updating-your-pull-request-branch You want to be sure to use the...

I need to find time to sit down with the query and understand it. Even after your explanation I'm having a hard time understanding the intention of the CROSS JOIN....

Can you provide an example redacted log entry? That would help narrow down the bad code. I can't find anywhere that doesn't redact the password when logging.

@EvertonCalgarotto That log entry looks like it's from an old version of the exporter. What version are you using?

v0.10.1 is very old. The most recent is v0.15.0. That log entry should not happen on the most recent version.

It looks like the cause there is that the old redaction func is [not accounting for the key=value style of DSN](https://github.com/prometheus-community/postgres_exporter/blob/master/cmd/postgres_exporter/util.go#L210). The [newer structures](https://github.com/prometheus-community/postgres_exporter/blob/master/config/dsn.go#L36) for DSN do account for this....