query to custom database.

[kilin-s]

Hello,
I want to use queries.yaml for request to my custom postgres databases, but i don't understand how. Shold i use database name in DSN like this :
DATA_SOURCE_NAME=postgresql://postgres_exporter:password@localhost:5432/my_custom_db?sslmode=disable
or i can set database in queries.yaml?

[kilin-s]

And how often query is execute?

[uspen]

That is unnecessary.
But if you need to request for example pg_stat_user_tables you need connect to custom db

[wrouesnel]

This is something I've not actually tried directly myself. A documentation improvement would be welcome so we can give a canonical example.

[wrouesnel]

Noted that we want to support some syntax in queries.yaml for multi-database queries.

[imatpro]

Hi,

any news on this features?

i would like use query.yaml for execute custom query in MYDB1, or MYDB2 or MYDB3.

thanks

[wrouesnel]

Probably pending the librarification of the collector, since functionally it's a bunch of collectors being aggregated, with only one including the default metrics.

[imatpro]

I resolve my problem with this exporter : https://github.com/justwatchcom/sql_exporter

[ipolishchuk]

After using postgres_exporter for a while on single database instances and loving it, it was a rude awakening to discover that I cannot collect custom metrics on multi-database instances. Is there any rough time estimate when it might become available?

[mubn]

Is there any news about this feature?

[wrouesnel]

Probably needs some ability to map multiple queries.yml files to individual DSNs.

[isaiasanchez]

Expanding the Auto-discover Databases you can add a value in queries.yaml like: database: for example, and the query will only be executed in those databases matching that list, something like:

pg_custom_query:
   query: "SELECT somelabel, somemetric FROM  sometable"
   database: "mydb1,mydb2"
   metrics:
     - somelabel:
           usage: "LABEL"
     - somemetric:
           usage: "GAUGE"

This query will only be executed when mydb1 and/or mydb2 are discovered in the instance.

In that way custom queries can be executed together with other queries using master: "true"