Monitoring

Monitoring replication setups is important to ensure that your system:

• Performs optimally

• Doesn’t run out of disk space

• Doesn’t encounter other faults that might halt operations

It’s important to have automated monitoring in place to ensure that the administrator is alerted and can take proactive action when issues occur. For example, the administrator can be alerted if replication slots start falling badly behind,

EDB provides Postgres Enterprise Manager (PEM), which supports PGD starting with version 8.1. See Monitoring EDB Postgres Distributed for more information.

Alternatively, tools or users can make their own calls into information views and functions provided by the BDR extension. See Monitoring through SQL for details.

EDB Postgres Distributed also integrates with OpenTelemetry, allowing you to use an existing reporting setup to follow the state of the EDB Postgres Distributed cluster. See OpenTelemetry integration for details.

• OpenTelemetry integration
  • OTEL and OLTP compatibility
  • Metrics collection
    • Generic metrics
    • Replication metrics
    • Consensus metric
  • Tracing
  • TLS support
• Monitoring through SQL
  • Monitoring overview
  • Monitoring node join and removal
  • Monitoring Replication Peers
    • Monitoring outgoing replication
    • Monitoring incoming replication
    • Monitoring WAL senders using LCR
  • Monitoring PGD replication workers
  • Monitoring PGD writers
  • Monitoring global locks
  • Monitoring conflicts
  • Apply statistics
  • Standard PostgreSQL statistics views
  • Monitoring PGD versions
  • Monitoring Raft consensus
  • Monitoring replication slots
  • Monitoring transaction COMMITs