cloudnative-pg / cloudnative-pg/charts
Instrumentation for pgStatStatements and logicalReplication queries not adding customQueriesConfigMap
- Dominant language
- Go Template
- Stars
- 621
- Forks
- 265
- Avg merge
- 7d 12h
- Merged PRs (30d)
- 7
Description
### Description
Enabling the pg_stat_statements extension on the chart with `cluster.monitoring.instrumentation.pgStatStatements: true` correctly enables the extension, creates the configmaps with the queries `-monitoring-logical-replication`, `-monitoring-pg-stat-statements` but does not add them to the `customQueriesConfigMap` on the cluster.
### Result
No metrics are emited for pgStatStatements and logicalReplication.
The cluster only has the injected cnpg-default-monitoring.
### Expected Result
When enabling the instrumentation the metrics should be emited by the pod, so they should be mounted.
I can make a PR for this
Contributor guide
Research direction
Start by locating the chart templates handling cluster.monitoring.instrumentation.pgStatStatements and customQueriesConfigMap, then trace how the logical-replication and pg-stat-statements query ConfigMaps are connected to the cluster. Done means enabling the instrumentation mounts both query sets and the pod emits their metrics; the payload names no specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 66/100