Remove pmm-server PostgreSQL instance from Query Analytics and Dashboards default view

For QAN, PMM has native capability to parse query comments. Why not simply comment/tag all PGSQL PMM queries, and filter them by default?

Hi,

I would keep collecting data from PMM instance as well but in default I would might hide it (but you could easily show them) or as PZ suggested I would have a separate menu where you would see the system metrics or the health of PMM installation which could include PG and even data from clickhouse and victoriametrics as well.. that would be even more important when we start providing PMM HA and you want to monitor the health of these databases …

Hi,

How it should be properly done is you put the PMM in its own environment -
"system" or something like that where you do not show it by default

Disabling PMM monitoring is silly as it can have performance problems on
its own... but it is different use case for the different user and should
not be mixed with "normal" traffic

Hi , saw your most recent note - may I suggest that we don’t actually wait for the 1st service to be added, instead disable the pmm-server from Query Analytics by default always.

An “empty” PMM Server (no services yet added), when viewing Query Analytics could instead have a note indicating that the queries will be available after they add a service. The point of this ticket is that when you go in QAN you should only ever see queries related to your application.

Regarding the PMM internal dashboards please don’t change anything there, they are available when needed to identify bottlenecks with metrics ingestion and display.

This happened with my current ongoing customer and they were confused that how come PG is showing here when they don't have any PG instance. Creating a tag or at least some comments ( like this is for PMM server) can clear out these confusions.