Isaias Sanchez

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:...

Well I was suggesting these configuration for developers to implement it in future version of the exporter, right now it doesn't work. Now what you can do is something like:...

there are two queries for pg_stat_statements, the one you are refering has the condition to run in PG greater that 13: ``` if instance.version.GE(semver.MustParse("13.0.0")) { query = pgStatStatementsNewQuery } ```...

After this WARN the exporter stops giving results, at lease un my case: curl http://localhost:9500/metrics curl: (18) transfer closed with outstanding read data remaining

You must check that the extension is created in every database apart from template ones. postgres database and the application databases as well, execute the CREATE EXTENSION command on all...

I'm arriving late to this discussion, i don't know if it's related with having two entries in pg_stat_statements with same queryid, this is related to the pg_stat_statements.track = 'all' witch...

I start seeing this error, have been a solution applied? is there a workaround we can implement? when this error occurs the exporter doesn't expose any metric. the error is...

The metric display the auto-vacuum duration, but normally there are more than one autovacuum running at the same time, and this fails with one of them having that field NULL....

FYI, I make a local build using the `COALESCE(xact_start,now())` and I got the following error. `An error has occurred while serving metrics: collected metric "pg_stat_activity_autovacuum_timestamp_seconds" { label:{name:"relname" value:"device_identifier"} gauge:{value:1.722847480622177e+09}} was...

the error is because the metric only shows the relname, but not schema and this DB has relations with same name but in different schemas. For version 14+: `SPLIT_PART(query, '...