You should be able to use these dashboards. It were designed for PMM1 so no specific PMM2 variables are used yet (e.g. node_name, service_name …)

Is it possible to use this dashboard with already installed postgres_exporter from scratch, together with modified queries.yaml? Not to install PMM client separately? This is because i already have Prometheus and Grafana in environment and we have no need for PMM Server.

BR.
Savo

First , Thanks for the reply. It resolved after increasing the METRICS_RESOLUTION=5s

Thanks
Siddesh

Maybe the issue is related to amount of information as a result of used custom query.
Could you test with a simple custom query?
e.g.
https://gist.github.com/adivinho/6e6b938f276932b867fb44b8e007df65

i tried with same Server and client version 1.17.3 .. with extend-query-path not working …

time=”2020-03-31T09:35:20Z” level=info msg=”Starting postgres_exporter (version=, branch=, revision=)” source=”postgres_exporter.go:1132″
time=”2020-03-31T09:35:20Z” level=info msg=”Build context (go=go1.10.1, user=, date=)” source=”postgres_exporter.go:1133″
time=”2020-03-31T09:35:20Z” level=info msg=”Established new database connection.” source=”postgres_exporter.go:1015″
time=”2020-03-31T09:35:20Z” level=info msg=”Semantic Version Changed: 0.0.0 -> 11.2.0″ source=”postgres_exporter.go:945″
time=”2020-03-31T09:35:20Z” level=info msg=”Starting HTTP server for http://1x.1xx.1xx.2×1:9187/metrics …” source=”server.go:121″

Typo in my pmm-server version .. its pmm-server-1.16.0-12

Thanks
Siddesh

Please help …

I have installed PMM1.6 and PMM client 1.71 , Node exprter working fine . Postgresql_exprters also working fine.

But when i removed and added postgresql exporter with extend query pmm-admin check-network showing down..

[root@sl73gseldbd192 prometheus]# pmm-admin add postgresql:metrics –user pmm_user –password secret postgres –host slxxxldbd192 –port 5432 –service-port 9187 –disable-ssl –extend.query-path /pgworkspace/software/prometheus/queries.yaml

* Connection: Client <– Server
——————- ————— ——————— ——- ———- ———
SERVICE TYPE NAME REMOTE ENDPOINT STATUS HTTPS/TLS PASSWORD
——————- ————— ——————— ——- ———- ———
linux:metrics slxxxldbd192 10.160.109.221:9100 OK NO –
postgresql:metrics postgres 10.160.109.221:9187 DOWN NO –

PMM Server | slxxxeldbd217 (insecure SSL)
Client Name | sxxxseldbd192.visa.com
Client Address | 10.1xx0.1xx9.xx21
Service Manager | linux-systemd

——————- ————— ———– ——– ——————————————– ————
SERVICE TYPE NAME LOCAL PORT RUNNING DATA SOURCE OPTIONS
——————- ————— ———– ——– ——————————————– ————
linux:metrics sl7xxldbd192 9100 YES – scheme=http
postgresql:metrics postgres 9187 YES postgresql:***@sl73gxxxd192:5432/postgres scheme=http

pmm_user=# show is_superuser
pmm_user-# ;
is_superuser
————–
on
(1 row)

Great tutorial.

Can I and/or how can I add –extend.query-path on linux docker postgres exporter?

What PMM version is used?

Here are commands for PMM 2.x versions
$ pmm-admin remove postgresql
$ docker exec -it pmm-server pmm-admin list –server-url=http://username:password@localhost/

thank you for this nice tutorial!

I have a question regarding pmm-admin rm postgresql:metrics PS_NODE-1 part….I get a massage :

pmm-admin: error: enum value must be one of mysql,mongodb,postgresql,proxysql, got ‘postgresql:metrics’, try –help

Also when I try docker exec -it pmm-server pmm-admin list , it says: Unauthorized. Please check username and password.

BR

Nenad

e.g.
pguser=# show is_superuser;
is_superuser
————–
on
(1 row)

pguser=# select count(*) from pg_stat_statements;
-[ RECORD 1 ]
count | 36

I actually installed and when i ran postgres_exporter with –extend.query-path its still throwing error
INFO[0173] Error running query on database “localhost:5432”: pg_stat_statements pq: relation “pg_stat_statements” does not exist source=”postgres_exporter.go:1286″

I actually installed and when i ran postgres_exporter with –extend.query-path its still throwing error
INFO[0173] Error running query on database “localhost:5432”: pg_stat_statements pq: relation “pg_stat_statements” does not exist source=”postgres_exporter.go:1286″

Could you use a full path to your file for the flag extend.query-path?
e.g.
–extend.query-path /home/username/queries2.yaml

[~]# pmm-admin add postgresql:metrics –host=localhost –password=yyy –port=5432 –user=xxx — –extend.query-path ./queries2.yaml
OK, now monitoring PostgreSQL metrics using DSN postgresql:***@localhost:5432/postgres
[root@db0pg1-1-prd ~]# pmm-admin list
pmm-admin 1.17.0

PMM Server | 10.252.203.232
Client Name | db0pg1-1-prd.eng.sfdc.net
Client Address | 10.252.203.232
Service Manager | linux-systemd

——————- ————————– ———– ——– ————————————— ——–
SERVICE TYPE NAME LOCAL PORT RUNNING DATA SOURCE OPTIONS
——————- ————————– ———– ——– ————————————— ——–
linux:metrics xxxxxx 42000 YES –
postgresql:metrics xxxxx 42005 YES postgresql:***@localhost:5432/postgres