ApsaraDB RDS for MySQL provides various performance metrics and supports custom views. You can select metrics to create custom views based on your business requirements. ApsaraDB RDS for MySQL provides powerful diagnostic capabilities to detect events on your RDS instance at the earliest opportunity and automatically diagnose the events to analyze root causes and provide suggestions. ApsaraDB RDS for MySQL also allows you to select a time period during which you want to perform manual diagnostics. This helps you understand the status of your RDS instance.

Description

The standard monitoring feature of ApsaraDB RDS for MySQL is upgraded and integrated with the performance trend feature of Database Autonomy Service (DAS) to provide more performance monitoring metrics and support custom views. You can select metrics to create custom views based on your business requirements. For more information, see Performance trends. ApsaraDB RDS for MySQL provides powerful diagnostic capabilities to detect events on your RDS instance at the earliest opportunity and automatically diagnose the events to analyze root causes and provide suggestions. ApsaraDB RDS for MySQL also allows you to select a time period during which you want to perform manual diagnostics.

  • For more information about the performance parameters that are related to the metrics, see Performance parameters.
  • DAS is a stable, secure, and efficient cloud service that is designed based on machine learning and expert experience to implement automated perception, recovery, optimization, O&M, and security assurance for databases. DAS helps prevent service failures that are caused by manual operations. For more information, see DAS overview.

View standard monitoring information

  1. Access RDS Instances, select a region at the top, and then click the ID of the target RDS instance.
  2. In the left-side navigation pane, click Monitoring and Alerts.
  3. On the Standard Monitoring tab, click the Standard View or Custom View tab.
    • On the Standard View tab, select a time range to view the trend of metrics and the statistics of various events.
      Note When you specify a time range, the end time must be later than the start time, and the interval between the start time and the end time cannot exceed 30 days.
      • Click View Details to go to the Performance Events tab. On the Performance Events tab, you can view the details of exception events, optimization events, and auto scaling events. The events include the events that are to be executed, the events that are being executed, and the events that are completed.
      • You can click More Metrics to select the metrics that you want to view. For more information about the monitoring items and metrics, see Monitoring items and metrics.
      • You can select the severity levels of events. If events of the selected severity levels are detected, the system displays the detected events in the MySQL CPU Utilization/Memory Usage and Session trend charts.

        You can click an event in a trend chart to view the diagnosis result in the event details.

        Event monitoring
      • You can click Add Trend Comparison to view the comparison of performance trends in a specific time range based on the metrics.
      • You can specify a time range and click Diagnose in the trend chart of a monitoring item to analyze the metrics for the selected time range.
      • You can click Common Causes in the trend chart of a monitoring item to view the common causes for the exceptions to the monitoring item.
      • You can click Details in the trend chart of a monitoring item to expand the chart. You can also change the time range to view the change trends of the monitoring item in a specific time range.
    • On the Custom View tab, click Add Monitoring Dashboard to create a custom dashboard to display the metrics that you want to monitor.
      • You can click Add Node and Metrics to select the nodes and metrics for the dashboard. For more information about the metrics, see Monitoring items and metrics.
      • You can set the Display Mode parameter to Merge Display or Separate Display.
        • If you select Merge Display, multiple metrics are displayed in the same trend chart.
        • If you select Separate Display, each metric is displayed in a separate trend chart.
          • You can configure the Chart Layout parameter to specify the number of trend charts of metrics in each row.
          • You can click Details in the trend chart of a metric to expand the chart. You can also change the time range to view the change trends of the metric in a specific time range.
    The following table describes the monitoring items and metrics.
    Monitoring item Metric
    MySQL CPU Utilization/Memory Usage
    • mysql.mem_usage: the memory usage of the RDS instance within the operating system.
    • mysql.cpu_usage: the CPU utilization of MySQL processes. The maximum value of this metric is 100% for ApsaraDB RDS instances.
    MySQL Storage Space Used (MB) The storage usage of the RDS instance. The monitoring item consists of the following metrics:
    • mysql.instance.size: the total storage usage of the RDS instance.
    • mysql.data.size: the amount of storage that is occupied by data files.
    • mysql.log.size: the amount of storage that is occupied by log files.
    • mysql.tmp.size: the amount of storage that is occupied by temporary files.
    • mysql.other.size: the amount of storage that is occupied by system files.

    Unit: MB.

    MySQL IOPS mysql.iops: the IOPS of the RDS instance.
    IOPS Usage mysql.iops_usage: the IOPS usage of the RDS instance.
    Session The sessions of the RDS instance. The monitoring item consists of the following metrics:
    • mysql.total_session: all sessions.
    • mysql.active_session: active sessions.
    Traffic Throughput (KB) The volumes of inbound and outbound traffic of the RDS instance per second. The monitoring item consists of the following metrics:
    • mysql.bytes_received: the average number of bytes of data that are received from all clients per second.
    • mysql.bytes_sent: the average number of bytes of data that are sent to all clients per second.

    Unit: KB.

    InnoDB Buffer Pool Requests
    • mysql.innodb_buffer_pool_reads_requests: the average number of logical page reads from the InnoDB buffer pool per second.
    • mysql.innodb_buffer_pool_write_requests: the average number of page writes to the InnoDB buffer pool per second.
    InnoDB Buffer Pool Hit Ratio
    • mysql.innodb_bp_dirty_pct: the ratio of dirty pages in the InnoDB buffer pool.
    • mysql.innodb_bp_hit: the read hit ratio of the InnoDB buffer pool.
    • mysql.innodb_bp_usage_pct: the utilization of the InnoDB buffer pool.
    InnoDB Redo Writes
    • mysql.innodb_log_writes: the average number of physical writes to the InnoDB redo log file per second.
    • mysql.innodb_os_log_fsyncs: the average fsync() writes to the log file per second.
    InnoDB Row Operations
    • mysql.innodb_rows_deleted: the average number of rows that are deleted from the InnoDB table per second.
    • mysql.innodb_rows_read: the average number of rows that are read from the InnoDB table per second.
    • mysql.innodb_rows_inserted: the average number of rows that are inserted to the InnoDB table per second.
    • mysql.innodb_log_writes: the average number of physical writes to the InnoDB redo log file per second.
    • mysql.innodb_rows_updated: the average number of rows that are updated in the InnoDB table per second.
    MyISAM Reads and Writes
    • mysql.MyISAM_key_reads: the number of physical reads by MyISAM per second.
    • mysql.MyISAM_key_read_requests: the number of reads from the buffer pool by MyISAM per second.
    • mysql.MyISAM_key_writes: the number of physical writes by MyISAM per second.
    • mysql.MyISAM_key_write_requests: the number of writes to the buffer pool by MyISAM per second.
    MyISAM Key Buffer Read Hit Ratio, Write Hit Ratio, and Usage (%)
    • mysql.MyISAM_key_write_hit_ratio: the average write hit ratio of the MyISAM key buffer per second.
    • mysql.MyISAM_key_usage_ratio: the average usage of the MyISAM key buffer per second.
    • mysql.MyISAM_key_read_hit_ratio: the average read hit ratio of the MyISAM key buffer per second.
    Replication Thread Status of Secondary Instances
    • mysql.slave_io_running: indicates whether the I/O thread that reads the source binary log is running.
    • mysql.slave_sql_running: indicates whether the SQL thread that executes the event in the relay log is running.
    Note
    • 1: indicates that the thread is running.
    • 0: indicates that the thread is lost.
    Replication Latency of Secondary Instances (second) mysql.slave_lag: the latency of data replication to the secondary RDS instance. Unit: seconds.
    Executions
    • mysql.insert_select: the average number of INSERT...SELECT statements that are executed per second.
    • mysql.insert_ps: the average number of INSERT statements that are executed per second.
    • mysql.select_ps: the average number of SELECT statements that are executed per second.
    • mysql.replace_select: the average number of REPLACE...SELECT statements that are executed per second.
    • mysql.update_ps: the average number of UPDATE statements that are executed per second.
    • mysql.delete_ps: the average number of DELETE statements that are executed per second.
    • mysql.replace_ps: the average number of REPLACE statements that are executed per second.
    Threads
    • mysql.threads_connected: the total number of threads.
    • mysql.threads_running: the number of active threads.
    MySQL_SelectScan mysql.select_scan: the number of full table scans.
    Note You can click the Monitoring metrics icon on the right of a monitoring item in a dashboard on the Standard Monitoring tab to view the description of the monitoring item.

View legacy monitoring information

  1. Access RDS Instances, select a region at the top, and then click the ID of the target RDS instance.
  2. In the left-side navigation pane, click Monitoring and Alerts.
  3. On the Legacy Monitoring tab, click Resource Monitoring, Engine Monitoring, or Deploy Monitoring. Then, specify a time range. If you use RDS Cluster Edition, you can also select an cluster ID or node ID. The following table describes the monitoring items and metrics.
    Note When you specify a time range, the end time must be later than the start time, and the interval between the start time and the end time cannot exceed 30 days.
    Monitoring type Monitoring item Description
    Resource Monitoring CPU Utilization and Memory Usage (%) The CPU utilization and memory usage of the RDS instance. This excludes the CPU utilization and memory usage of the operating system.
    Disk Space (MB) The disk usage of the RDS instance. The disk usage provides the following information:
    • Disk Space Used
    • Data Space Used
    • Log Space Used
    • Temporary File Space Used
    • System File Space Used

    Unit: MB.

    IOPS The IOPS of the RDS instance.
    Total Connections The number of active connections to the RDS instance and the total number of connections to the RDS instance.
    Network Traffic (KB) The volumes of inbound and outbound traffic of the RDS instance per second. Unit: KB.
    Engine Monitoring Transactions per Second (TPS)/Queries per Second (QPS) The average number of transactions per second (TPS) 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 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 Reads, Writes, and fsync() Operations The number of physical writes to log files by InnoDB per second, the number of log write requests by InnoDB per second, and the number of fsync writes to log files by InnoDB per second.
    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. The following items are included:
    • 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 Reads and Writes 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 Thread Status The number of active threads and the number of connected threads.
    Note The number of active threads may be greater than the number of connected threads. This is because threads may be used for other workloads than connection establishments.
    Redo Log Size Written by InnoDB per Second (Bytes/s) The amount of log data that is written to the redo log files per second. Unit: bytes.
    MySQL_ROW_LOCK The information about row-level locks in InnoDB. The monitoring item consists of the following metrics:
    • innodb_row_lock_waits: the average number of times the row-level locks have been waited for.
    • innodb_row_lock_time: the maximum time of a row-level lock that has been waited for. Unit: milliseconds.
    • innodb_row_lock_avg: the average time of row-level locks that have been waited for. Unit: milliseconds.
    MySQL_SelectScan The number of full table scans.
    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.