Skip to content

Is there a Prometheus metric to indicate a PGO cluster is configured as standby? #4150

Open
@johnswarbrick-napier

Description

@johnswarbrick-napier

PGO version: 5.5.1
Postgres version: 13

I have configured my PostgreSQL cluster as a standby which is replicating with the primary through S3 object storage with a simple config option:

postgres:
  standby:
    enabled: true
    repoName: repo1

The cluster is successfully synchronising, but monitoring alerts are being triggered for backups not running and WAL logs not being archived by the standby - which is expected:

(ccp_archive_command_status_seconds_since_last_fail > 30) or (ccp_archive_command_status_archived_count == 0)
ccp_backrest_last_incr_backup_time_since_completion_seconds{stanza="db"} > 129600

Is there any Prometheus metric exported by PGO to indicate the cluster is running as a standby?

I was looking at pg_settings_hot_standby but that seems to indicate a replica rather than a cluster.

Thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions