The Standard Monitoring page provides two categories of metrics for an ApsaraDB RDS for MariaDB instance: resource metrics that reflect compute, storage, and network consumption, and engine metrics that reflect InnoDB and MyISAM internals. Use these metrics to diagnose performance issues and verify instance health.
Prerequisites
Before you begin, ensure that you have:
An ApsaraDB RDS for MariaDB instance
Access to the ApsaraDB RDS console
View monitoring metrics
Log on to the ApsaraDB RDS console.
In the left-side navigation pane, click Instances. In the top navigation bar, select the region of your instance.
Find the instance and click its ID.
In the left-side navigation pane, click Monitoring and Alerts.
On the Standard Monitoring tab, click Resource Monitoring or Engine Monitoring, then specify a time range to view the data.
Resource monitoring metrics
| Metric | Description | Units |
|---|---|---|
| IOPS | The number of input/output operations per second (IOPS) for the data disk and log disk. High IOPS relative to provisioned limits indicates I/O saturation. | Operations/s |
| CPU utilization and memory usage | The CPU utilization and memory usage of the instance. Sustained high values indicate that the instance is under heavy load and may need to be scaled up. | % |
| Disk space | The total disk usage broken down into: Disk Space Used, Data Space Used, Log Space Used, Temporary File Space Used, and System File Space Used. Monitor this metric to avoid running out of storage. | MB |
| Total connections | The number of active connections and the total number of connections to the instance. A high active-to-total ratio indicates connection pool pressure. | Count |
| Network traffic | The volume of inbound and outbound traffic per second. Spikes may indicate bulk data transfers or unexpected query loads. | KB |
Engine monitoring metrics
| Metric | Description | Units |
|---|---|---|
| Transactions per second (TPS) / Queries per second (QPS) | The average number of transactions per second (TPS) and the average number of SQL statements executed per second (QPS). A sudden drop in TPS or QPS may indicate a blocking transaction or lock contention. | Count/s |
| InnoDB buffer pool read hit ratio, usage ratio, and dirty block ratio | The read hit ratio, usage ratio, and dirty block ratio of the InnoDB buffer pool. A low read hit ratio (below 95%) means frequent disk reads; a high dirty ratio means many modified pages have not been flushed to disk. | % |
| InnoDB read/write volume | The amount of data that InnoDB reads from and writes to disk per second. Consistently high write volume may indicate write-heavy workloads that benefit from optimized I/O. | KB |
| InnoDB buffer pool read/write frequency | The number of logical read and write operations that InnoDB performs against the buffer pool per second. | Count/s |
| InnoDB log reads, writes, and fsync() operations | The average frequency of physical writes to log files, the frequency of log write requests, and the average frequency of fsync() calls per second. High fsync() frequency with slow commit times indicates an I/O bottleneck on the log disk. | Count/s |
| Temporary tables created on hard disk | The number of temporary tables automatically created on the hard disk when SQL statements execute. High counts indicate that queries are spilling to disk; optimize queries or increase tmp_table_size. | Count |
| MySQL_COMDML | The number of each SQL statement type executed per second: Insert, Delete, Insert_Select, Replace, Replace_Select, Select, and Update. Use this metric to understand the read/write ratio and identify dominant query types. | Count/s |
| MySQL_RowDML | The number of row-level operations that InnoDB performs per second, including physical writes to log files and rows read, updated, deleted, and inserted in InnoDB tables. | Count/s |
| MyISAM reads and writes | The number of reads and writes to the MyISAM buffer pool per second, and the number of reads and writes to hard disk per second. A high disk read or write count relative to buffer pool activity indicates that the MyISAM key buffer is too small. | Count/s |
| MyISAM key buffer read/write/usage ratio | The read hit ratio, write hit ratio, and usage of the MyISAM key buffer per second. Low read or write hit ratios indicate that the key buffer is too small for your working set. | % |