New observability metrics are not available

[maxim-mityutko]

According to the docs, I'm expecting to see 3 new backup metrics, instead of the old ones. However despite the fact that backup through plugin is configured and working, the metrics are not popping up. And the old metrics are no longer working of course. Now I'm a bit lost, is there a problem with my config?

Plugin is installed via Helm:
https://github.com/maxim-mityutko/home-infra/blob/efc76d0398d9f46d65d8e2a72143bd5d4b0e742c/kubernetes/cluster/default/cloudnative-pg/kustomization.yaml#L40-L56

Plugin Configuration in CNPG Cluster

  plugins:
    - name: barman-cloud.cloudnative-pg.io
      enabled: true
      isWALArchiver: false
      parameters:
        serverName: cnpg-default
        barmanObjectName: cnpg-default-barman

Objectstore

apiVersion: barmancloud.cnpg.io/v1
kind: ObjectStore
metadata:
  name: cnpg-default-barman
spec:
  retentionPolicy: 7d
  instanceSidecarConfiguration:
    retentionPolicyIntervalSeconds: 21600 # 6 hours
    resources:
      requests:
        memory: 100Mi
        cpu: 100m
      limits:
        memory: 500Mi
        cpu: 2
  configuration:
    destinationPath: s3://cnpg-backup/
    endpointURL: <url>
    s3Credentials:
      accessKeyId:
        name: cnpg-default-secret
        key: username
      secretAccessKey:
        name: cnpg-default-secret
        key: password
    data:
      compression: bzip2
    wal:
      compression: bzip2

Backup

apiVersion: postgresql.cnpg.io/v1
kind: ScheduledBackup
metadata:
  name: cnpg-default-backup
spec:
  immediate: true
  schedule: "0 0 2 * * *"
  backupOwnerReference: self
  cluster:
    name: cnpg-default
  method: plugin
  pluginConfiguration:
    name: barman-cloud.cloudnative-pg.io

Environment

• plugin-barman-cloud:v0.9.0
• postgresql:17.4
• cloudnative-pg:1.28.0

[dosubot]

Hi @maxim-mityutko! I'm Dosu and I’m helping the plugin-barman-cloud team.

The new backup metrics with the barman_cloud_cloudnative_pg_io_ prefix are implemented and should be exposed by the barman-cloud plugin, but there are a few common reasons they might not appear even if backups are working:

1. The metrics are exposed by the controller-manager pod (the plugin operator) via the /metrics endpoint (usually port 8443) in the system or cnpg-system namespace, not by the PostgreSQL pods or sidecars. Make sure your Prometheus is scraping the controller-manager-metrics-service in the correct namespace and on the right port and path /metrics.

2. If the ObjectStore status does not contain the expected serverName key (matching your plugin config), the metrics will return zero values. Double-check that the serverName in your plugin config matches the key in the ObjectStore's status.ServerRecoveryWindow field metrics.go.

3. After deploying or upgrading the plugin, you must restart the CloudNativePG operator (controller-manager) so it can detect and register the plugin. If you haven't done this, metrics may not appear even if everything else looks correct issue #655.

4. For S3-compatible storage, you may need to set AWS_REQUEST_CHECKSUM_CALCULATION and AWS_RESPONSE_CHECKSUM_VALIDATION to when_required in your ObjectStore's instanceSidecarConfiguration.env to avoid silent failures issue #655.

5. If all of the above are correct and you still don't see the metrics, check the logs for the controller-manager and plugin sidecar for errors related to metrics, registration, or ObjectStore access.

The metrics you should see are:

• barman_cloud_cloudnative_pg_io_last_failed_backup_timestamp
• barman_cloud_cloudnative_pg_io_last_available_backup_timestamp
• barman_cloud_cloudnative_pg_io_first_recoverability_point

These replace the old cnpg_collector_* metrics, which are deprecated and no longer updated after migration to the plugin-based backup architecture observability.md.

If you check these areas and still have issues, sharing the output of kubectl get pods, kubectl get objectstore, and kubectl get service in the relevant namespace, along with relevant logs, will help pinpoint the problem.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}