This topic describes how to view the resource metrics, engine metrics, and deployment metrics of an ApsaraDB RDS for MySQL instance in the ApsaraDB RDS console.

View standard monitoring information

  1. Visit the RDS instance list, select a region above, and click the target instance ID.
  2. In the left-side navigation pane, click Monitoring and Alerts.
  3. On the Standard Monitoring tab, select the Resource Monitoring, Engine Monitoring, or Deploy Monitoring type and specify a time range. Then, view the metrics that appear. The following table describes the metrics.
    Monitoring type Metric Description
    Resource Monitoring Disk Space (MB) The disk usage of your RDS instance. The disk usage provides the following information:
    • Instance Size
    • Data Usage
    • Log Size
    • Temporary File Size
    • Other system file size

    Unit: MB.

    IOPS The IOPS of your RDS instance.
    Total Connections The number of active connections to your RDS instance and the total number of connections to your RDS instance.
    CPU Utilization and Memory Usage (%) The CPU utilization and memory usage of your RDS instance. This excludes the CPU utilization and memory usage for the operating system.
    Network Traffic (KB) The volume of inbound and outbound traffic of your RDS instance per second. Unit: KB.
    Engine Monitoring TPS/QPS The average number of transactions per second and the average number of SQL statements that are executed per second.
    InnoDB Buffer Pool Read Hit Ratio, Usage Ratio, and Dirty Block Ratio (%) The read hit ratio, usage, and dirty block ratio of the InnoDB buffer pool.
    InnoDB Read/Write Volume (KB) The amount of data that InnoDB reads and writes per second. Unit: KB.
    InnoDB Buffer Pool Read/Write Frequency The number of read and write operations that InnoDB performs per second.
    InnoDB Log Read/Write/fsync The average frequency of physical writes to log files per second by InnoDB, the frequency of log write requests, and the average frequency of fsync writes to log files.
    Temporary Tables Automatically Created on Hard Disk when MySQL Statements Are Executed The number of temporary tables that are automatically created on the hard disk when SQL statements are executed.
    MySQL_COMDML The number of SQL statements that are executed per second. ApsaraDB RDS supports the following SQL statements:
    • Insert
    • Delete
    • Insert_Select
    • Replace
    • Replace_Select
    • Select
    • Update
    MySQL_RowDML The number of operations that InnoDB performs per second, including:
    • The number of physical writes to log files per second.
    • The number of rows on which InnoDB performs operations per second. This includes the number of rows that are read from InnoDB tables per second, the number of rows that are updated in InnoDB tables per second, the number of rows that are deleted from InnoDB tables per second, and the number of rows that are inserted into InnoDB tables per second.
    MyISAM Read/Write Frequency The number of reads from the buffer pool by MyISAM per second, the number of writes to the buffer pool by MyISAM per second, the number of reads from the hard disk by MyISAM per second, and the number of writes to the hard disk by MyISAM per second.
    MyISAM Key Buffer Read/Write/Usage Ratio (%) The read hit ratio, write hit ratio, and usage of the MyISAM key buffer per second.
    MySQL_ThreadStatus The number of active threads and the number of connected threads.
    Note The number of active threads may be grater than the number of connected threads. This is because threads may be used for other workloads than connection establishments.
    InnoDB writes Redo Log per second (bytes/s) The amount of log data that is written to the redo log files per second. Unit: byte.
    Deploy Monitoring Replication Thread Status of Secondary Instances The status of the threads that are used to replicate data to the secondary RDS instance.
    • I/O Thread Status of Secondary Instances: The value 1 indicates that the thread is normal, and the value 0 indicates that the thread is lost.
    • SQL Thread Status of Secondary Instances: The value 1 indicates that the thread is normal, and the value 0 indicates that the thread is lost.
    Replication Latency of Secondary Instances (s) The latency of data replication to the secondary RDS instance. Unit: seconds.

View advanced monitoring information

  1. Visit the RDS instance list, select a region above, and click the target instance ID.
  2. In the left-side navigation pane, click Monitoring and Alerts. On the page that appears, click the Advanced Monitoring tab.
    Note For more information about the metrics, see Dashboard.