diff --git a/platform/cnpg/alerts.yaml b/platform/cnpg/alerts.yaml
index b177c95..3c0621d 100644
--- a/platform/cnpg/alerts.yaml
+++ b/platform/cnpg/alerts.yaml
@@ -198,7 +198,7 @@ spec:
             severity: warning
           annotations:
             summary: "No recent CNPG base backup: {{ $labels.job }}"
-            description: "The most recent completed base backup for PostgreSQL cluster {{ $labels.job }} (namespace {{ $labels.namespace }}) is over 36h old — the daily ScheduledBackup has stopped producing backups, so the PITR window is ageing out against the 30d retentionPolicy. Per-CLUSTER: the newest timestamp across the cluster's instances is used, which is the primary's. Check `kubectl get backup -n {{ $labels.namespace }}`."
+            description: "The most recent completed base backup for PostgreSQL cluster {{ $labels.job }} (namespace {{ $labels.namespace }}) is over 36h old — the daily ScheduledBackup has stopped producing backups, so the PITR window is ageing out against the 30d retentionPolicy. Per-CLUSTER: the newest timestamp across the cluster's instances is used, which is the primary's. Check `kubectl get backups.postgresql.cnpg.io -n {{ $labels.namespace }}` — the FULLY-QUALIFIED name is required: longhorn.io, postgresql.cnpg.io and velero.io all register kind Backup, and bare `kubectl get backup` resolves to Longhorn's (empty) set and reports 'No resources found' while CNPG backups exist."
             runbook_url: "https://${BASE_DOMAIN}/runbooks/cnpg-backup-missed"
         # ---------------------------------------------------------------------------------------
         # WAL-VOLUME-SPECIFIC ESCALATION. pg_wal holds more segments than max_wal_size allows for,