Skip to content
logo
Percona XtraDB Cluster
Monitor the cluster
Initializing search
    percona/pxc-docs
    percona/pxc-docs
    • Home
      • About Percona XtraDB Cluster
      • Percona XtraDB Cluster limitations
      • Understand version numbers
      • Quick start guide for Percona XtraDB Cluster
      • Install Percona XtraDB Cluster
      • Configure nodes for write-set replication
      • Bootstrap the first node
      • Add nodes to cluster
      • Verify replication
      • High availability
      • PXC strict mode
      • Online schema upgrade
      • Non-Blocking Operations (NBO) method for Online Scheme Upgrades (OSU)
      • Security basics
      • Secure the network
      • Encrypt PXC traffic
      • Enable AppArmor
      • Enable SELinux
      • State snapshot transfer
      • Percona XtraBackup SST configuration
      • Restart the cluster nodes
      • Cluster failover
      • Monitor the cluster
        • Manual monitoring
        • Alerting
        • Metrics
        • Use Percona Monitoring and Management
        • Other reading
      • Certification in Percona XtraDB Cluster
      • Percona XtraDB Cluster threading model
      • Understand GCache and Record-Set cache
      • GCache encryption and Write-Set cache encryption
      • Perfomance Schema instrumentation
      • Data at Rest Encryption
      • Upgrade Percona XtraDB Cluster
      • Crash recovery
      • Configure Percona XtraDB Cluster on CentOS
      • Configure Percona XtraDB Cluster on Ubuntu
      • Set up Galera arbitrator
      • How to set up a three-node cluster on a single box
      • How to set up a three-node cluster in EC2 environment
      • Load balancing with HAProxy
      • Load balancing with ProxySQL
      • ProxySQL admin utilities
      • Setting up a testing environment with ProxySQL
      • Release notes index
      • Percona XtraDB Cluster 8.0.31-23 (2023-03-14)
      • Percona XtraDB Cluster 8.0.30-22.md (2022-12-28)
      • Percona XtraDB Cluster 8.0.29-21 (2022-09-12)
      • Percona XtraDB Cluster 8.0.28-19.1 (2022-07-19)
      • Percona XtraDB Cluster 8.0.27-18.1
      • Percona XtraDB Cluster 8.0.26-16.1
      • Percona XtraDB Cluster 8.0.25-15.1
      • Percona XtraDB Cluster 8.0.23-14.1
      • Percona XtraDB Cluster 8.0.22-13.1
      • Percona XtraDB Cluster 8.0.21-12.1
      • Percona XtraDB Cluster 8.0.20-11
      • Percona XtraDB Cluster 8.0.20-11.3
      • Percona XtraDB Cluster 8.0.20-11.2
      • Percona XtraDB Cluster 8.0.19-10
      • Percona XtraDB Cluster 8.0.18-9.3
      • Index of wsrep status variables
      • Index of wsrep system variables
      • Index of wsrep_provider options
      • Index of files created by PXC
      • Frequently asked questions
      • Glossary
      • Copyright and licensing information
      • Trademark policy

    • Manual monitoring
    • Alerting
    • Metrics
    • Use Percona Monitoring and Management
    • Other reading

    Monitor the cluster¶

    Each node can have a different view of the cluster. There is no centralized node to monitor. To track down the source of issues, you have to monitor each node independently.

    Values of many variables depend on the node from which you are querying. For example, replication sent from a node and writes received by all other nodes.

    Having data from all nodes can help you understand where flow messages are coming from, which node sends excessively large transactions, and so on.

    Manual monitoring¶

    Manual cluster monitoring can be performed using myq-tools.

    Alerting¶

    Besides standard MySQL alerting, you should use at least the following triggers specific to Percona XtraDB Cluster:

    • Cluster state of each node

    wsrep_cluster_status != Primary

    • Node state

    wsrep_connected != ON

    wsrep_ready != ON

    For additional alerting, consider the following:

    • Excessive replication conflicts can be identtified using the wsrep_local_cert_failures and wsrep_local_bf_aborts variables

    • Excessive flow control messages can be identified using the wsrep_flow_control_sent and wsrep_flow_control_recv variables

    • Large replication queues can be identified using the wsrep_local_recv_queue.

    Metrics¶

    Cluster metrics collection for long-term graphing should be done at least for the following:

    • Queue sizes:

    wsrep_local_recv_queue and wsrep_local_send_queue

    • Flow control:

    wsrep_flow_control_sent and wsrep_flow_control_recv

    • Number of transactions for a node:

    wsrep_replicated and wsrep_received

    • Number of transactions in bytes:

    wsrep_replicated_bytes and wsrep_received_bytes

    • Replication conflicts:

    wsrep_local_cert_failures and wsrep_local_bf_aborts

    Use Percona Monitoring and Management¶

    Percona Monitoring and Management includes two dashboards to monitor PXC:

    1. PXC/Galera Cluster Overview:

      image

    2. PXC/Galera Graphs:

      image

      These dashboards are available from the menu:

      image

    Please refer to the official documentation for details on Percona Monitoring and Management installation and setup.

    Other reading¶

    • Realtime stats to pay attention to in PXC and Galera

    Contact us

    For free technical help, visit the Percona Community Forum.

    To report bugs or submit feature requests, open a JIRA ticket.

    For paid support and managed or consulting services , contact Percona Sales.


    Last update: 2023-01-20
    Percona LLC and/or its affiliates, © 2023
    Made with Material for MkDocs

    Cookie consent

    We use cookies to recognize your repeated visits and preferences, as well as to measure the effectiveness of our documentation and whether users find what they're searching for. With your consent, you're helping us to make our documentation better.