MySQL InnoDB ClusterSet & Cluster Monitoring
Overview
MySQL InnoDB Cluster and InnoDB ClusterSet provide a high-availability and disaster recovery solution for MySQL deployments. Monitoring these clusters is essential to ensure continuous availability, replication consistency, and optimal performance across primary and replica clusters.With Applications Manager’s MySQL InnoDB ClusterSet & Cluster monitoring, you can gain deep visibility into cluster health, node status, replication behavior, and resource utilization.
Creating a new MySQL InnoDB ClusterSet & Cluster monitor
Prerequisites for monitoring MySQL InnoDB ClusterSet & Cluster metrics:Click here
Using the REST API to add a new MySQL InnoDB ClusterSet & Cluster monitor:Click here
To create a MySQL InnoDB ClusterSet & Cluster monitor, follow the steps given below:
- Click on the New Monitor link. Choose MySQL from the Database Servers category.
- Specify the Display Name for the MySQL InnoDB ClusterSet & Cluster monitor.
- Enter the Host Name/IP Address of any node that is part of the InnoDB Cluster.
- Provide the Port on which MySQL is running.
- Enter the Username and Password, or select the required credentials from the Credential Manager list after enabling the Select from credential list option.
- Enable the Discover MySQL InnoDB Cluster(s)checkbox to automatically discover cluster topology using the provided node credentials.
- If the provided credentials return ClusterSet or Cluster information, Applications Manager proceeds with discovery. Credentials of any cluster node can be used, as cluster metadata is available across all nodes.
- If a ClusterSet is detected, it is added as a parent monitor group.
- Clusters within the discovered ClusterSet are added as child monitor groups under the respective ClusterSet.
- If no ClusterSet is detected, but individual Clusters are available, each Cluster is added as a separate monitor group.
- All MySQL nodes within the discovered clusters (including nodes in both primary and replica clusters) are added and associated with their respective Cluster monitor groups.
- If node-level authentication fails using the provided credentials, the nodes are still added in an unauthenticated state. You can manually update credentials for these nodes after discovery.
- If neither ClusterSet nor Clusters are detected using the provided credentials, an alert is shown indicating that the node is not part of an InnoDB Cluster.
- Enter the Polling Interval time in minutes. The default value is 5 minutes.
- Choose the Monitor Group from the combo box to associate the monitor (optional).
- Click Add Monitor(s) to complete discovery and begin monitoring the MySQL InnoDB ClusterSet and Cluster environment.
Monitored Parameters
When you have successfully added a MySQL InnoDB ClusterSet & Cluster monitor, Applications Manager collects a set of key performance, availability, and replication metrics across the ClusterSet, individual Clusters, and MySQL nodes. These metrics help you assess the health of cluster components, node roles, replication status, query activity, and resource utilization.
Applications Manager displays the monitor in the Monitors tab, where you can view data in the Availability, Performance, and List View tabs:
- Availability tab gives the Availability history for the past 24 hours or 30 days.
- Performance tab gives the Health Status and events for the past 24 hours or 30 days.
- List View enables you to perform bulk admin configurations.
Click on the individual monitors listed to view the following metrics monitored as part of MySQL InnoDB ClusterSet & Cluster monitoring:
ClusterSet Monitor Group
| Parameters | Description |
|---|
| CLUSTERSET MONITOR GROUP |
| Domain Name | The name of the MySQL InnoDB ClusterSet. |
| Global Primary Instance | The primary instance of the primary cluster within the ClusterSet. This information is retrieved only when connected to the PRIMARY cluster. |
| Primary Cluster | The name of the primary cluster in the InnoDB ClusterSet. |
| Status | Indicates the health status of the primary cluster based on member availability. The cluster is considered HEALTHY when a majority of members are online; otherwise, it is marked as NOT TOLERANT. |
Cluster Monitor Group
| Parameters | Description |
|---|
| CLUSTER MONITOR GROUP |
| Cluster Name | The name of the MySQL InnoDB cluster. |
| Cluster Role | The role of the cluster within the ClusterSet. Possible values are PRIMARY or REPLICA. |
| Group Name | The name of the group to which the MySQL server member belongs. |
| Channel Name | The name of the Group Replication channel. |
| Replication Mode | The replication mode used by the group. Possible values are single-primary and multi-primary. |
| Primary Host | The host name of the primary member in the group. |
| Primary Port | The port number of the primary member in the group. |
| Replication Lag | For replica clusters, this indicates the replication lag from the primary cluster. |
| Availability | The availability status of the cluster monitor group. |
| Health | The overall health status of the cluster monitor group. |
MySQL Nodes
| Parameters | Description |
|---|
| MYSQL NODES |
| Node Name | The host name of the MySQL node participating in the cluster. |
| Target Address | The IP address of the MySQL node. |
| Port | The port on which the MySQL node is running. |
| Member Role | The role of the node within the cluster, either Primary or Secondary. |
| Cluster Name | The name of the cluster to which the node belongs. |
| Cluster Role | The role of the cluster to which the node belongs. Possible values are PRIMARY or REPLICA. |
| Count Conflicts Detected | The number of transactions that failed the conflict detection check. |
| Lag from Original Source (Seconds) | The time delay between the commit on the primary source and its application on the replica. |
| Lag from Immediate Source (Seconds) | The time delay between the commit on the immediate upstream source and its application on the replica. |
| Last Error | The most recent error message triggered on the MySQL node. |
| Last Error Timestamp | The timestamp at which the last error occurred. |
| Availability | The availability status of the MySQL node. |
| Health | The overall health status of the MySQL node. |
