PG version reported by Telemetry from PMM Server spoiling data
General
Escalation
General
Escalation
Description
How to test
None
How to document
None
relates to
Smart Checklist
Activity
Show:
Alexey Mukas August 1, 2022 at 3:33 AM
Roma Novikov July 22, 2022 at 12:30 PM
This need to go to 2.30 because of https://perconadev.atlassian.net/browse/PMM-5885#icft=PMM-5885
It will be very hard for us to split PG version between different PG used in PMM
Maxim Kondratenko June 2, 2022 at 8:52 AM
For the time being PMM collects Postgres metrics as following:
- id: PostgresDBVersion
source: VM
query: pg_static{service_type="postgresql"}
summary: "Version of monitored PostgreSQL services"
data:
- metric_name: "postgresql_version"
label: "short_version"Possible solution here may be:
- id: PostgresDBVersion
source: VM
query: pg_static{service_type="postgresql"} <<-- exclude here metrics related to PMM itself
summary: "Version of monitored PostgreSQL services"
data:
- metric_name: "postgresql_version"
label: "short_version"
- id: PostgresPMMDBVersion
source: VM
query: pg_static{service_type="postgresql"} <<-- filter here PMM Postgres only.
summary: "Version of monitored PostgreSQL services"
data:
- metric_name: "pmm_postgresql_version"
label: "short_version"
Done
Created June 1, 2022 at 3:10 PM
Updated March 6, 2024 at 1:01 AM
Resolved August 29, 2022 at 12:17 PM
The problem: PMM telemetry includes pmm-server data about PG Version and etc.
It's making it hard to create queries to analyze data as a person creating Query to Telemetry needs to exclude PMM data
On another side of this - as pmm PM, I need a date about the pmm server as this can help to find some problems..
Possible solution:
Split pmm-server metrics (currently only PG and Node data) into separate metrics and exclude pmm-server from general metrics.