Joe Adams

I don't think that pg_stat_statements is part of the default metrics exported by the exporter. Did you copy the example queries.yaml file and set it to be used with `--extend.query-path`...

I believe that @SuperQ is the one to merge. I don't have access on this repo. Ping. :)

It is not clear what you are asking. The screenshot looks like you are asking about an error connecting to your cluster due to an untrusted CA on the certificate....

Currently DSNs that are of the form "postgresql://" are parsed by the URL library. This means that special characters must be valid URLs.

This has already been fixed in the master branch.

I do not think that the context is propagated to any of the collectors at this time. While the http.Request may be cancelled by the header timeout, the downstream functions...

I'm not sure that I understand what this PR is trying to achieve. Can you provide a bit more context please?

When you query `_nodes/stats`, what is the value of `process.cpu.percent`? That's the exact value that should be returned by the exporter.

What version of elasticsearch are you using? This does not match the output from any version that I have tested against.

2.3 has bee EOL since 2017. https://www.elastic.co/support/eol I do not think that we will be making changes to the exporter to support such an old version at this point.