Instrumentation for pgStatStatements and logicalReplication queries not adding customQueriesConfigMap

[oscarbcala]

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 <cluster>-monitoring-logical-replication, <cluster>-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

[dosubot]

Hi @oscarbcala! I'm Dosu and I'm helping the CloudNativePG team.

Confirmed — this is a real gap in the chart's template logic. The monitoring-pg-stat-statements.yaml and monitoring-logical-replication.yaml templates correctly create their ConfigMaps when the respective instrumentation flags are enabled, but cluster.yaml never wires those ConfigMap names into spec.monitoring.customQueriesConfigMap. That block only ever adds the single <cluster>-monitoring ConfigMap, and only when cluster.monitoring.customQueries is non-empty [1] — there is no logic tied to instrumentation.pgStatStatements or instrumentation.logicalReplication at all.

For comparison, the user-supplied custom queries ConfigMap (<cluster>-monitoring) is generated in user-metrics.yaml and correctly gets added to customQueriesConfigMap when non-empty [2], but the two instrumentation-driven ConfigMaps were never appended to that same array. So CNPG never reads them, and no pg_stat_statements or logical replication metrics get emitted — matching what you're seeing (only cnpg-default-monitoring, which is injected by the operator itself, not the chart).

A PR that appends {{ include "cluster.fullname" . }}-monitoring-pg-stat-statements and {{ include "cluster.fullname" . }}-monitoring-logical-replication to the customQueriesConfigMap list in cluster.yaml, conditioned on the same instrumentation.pgStatStatements / instrumentation.logicalReplication flags, would fix this.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.