PMM-12888 Implemented new Patroni dashboard. #1566
Conversation
| "name": "replication_set", | ||
| "options": [], | ||
| "query": { | ||
| "query": "label_values({__name__=~\"pg_up|mysql_up|mongodb_up|proxysql_mysql_status_active_transactions\"}, replication_set)", |
There was a problem hiding this comment.
I wonder if querying for anything other than pg_up is of relevance here?
There was a problem hiding this comment.
Great question. I was not using this, and just opted for:
Environment / Cluster / Service Name / Scope Name
However, the pmm-admin add external command offers the --replication-set argument, so we could add it. The postgresql exporter also has this argument available, so this will boil down to how we want to do it for Postgres in general.
Let me know and I can do the changes.
There was a problem hiding this comment.
Let's keep it as is for Experimental.
If this is what I'm thinking - it's the "how to get the list of Replicas in general," and for now, we use the metrics, but when our inventory becomes more reliable ("labels auto discovery") - we must move it to be based on inventory, probably.
Co-authored-by: Alex Demidoff <[email protected]>
* PMM-12888 Implemented new Patroni dashboard. * Change dashboard UID to NULL. Co-authored-by: Alex Demidoff <[email protected]> --------- Co-authored-by: Roman Novikov <[email protected]> Co-authored-by: Alex Demidoff <[email protected]>
New dashboard as showcased in https://www.percona.com/blog/monitoring-a-postgresql-patroni-cluster/.
There are some minor differences with the one shown in the blog, like separating Patroni and Postrges configurations/panels. I think it's cleaner in this way. The WAL location graphs have hidden rate queries, which can be helpful in some cases, but also add a bit of noise. I was not sure what to do with them, so I decided to leave them disabled by default.
Let me know what you think about it.
Thanks!
FB: Percona-Lab/pmm-submodules#3546
https://perconadev.atlassian.net/browse/PMM-12888