Monitoring 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.
Besides standard MySQL alerting, you should use at least the following triggers specific to Percona XtraDB Cluster:
For additional alerting, consider the following:
- Excessive replication conflicts can be identtified using the
- Excessive flow control messages can be identified using the
- Large replication queues can be identified using the
Cluster metrics collection for long-term graphing should be done at least for the following:
- Queue sizes:
- Flow control:
- Number of transactions for a node:
- Number of transactions in bytes:
- Replication conflicts:
Using Percona Monitoring and Management¶
Percona Monitoring and Management includes two dashboards to monitor PXC:
These dashboards are available from the menu:
Please refer to the official documentation for details on Percona Monitoring and Management installation and setup.