Database Autonomy Service (DAS) continuously monitors core metrics of your ApsaraDB RDS for MySQL instance using machine learning and intelligent algorithms to detect anomalies and predict issues. When an anomaly appears, use the one-click diagnostics feature to identify the root cause.
Prerequisites
Before you begin, make sure that:
The database instance is an ApsaraDB RDS for MySQL instance
The database instance is connected to DAS and in the Normal Access state. For more information, see Connect an Alibaba Cloud database instance to DAS
Detect and diagnose performance anomalies
Log on to the DAS console.
In the left-side navigation pane, click Instance Monitoring.
Find the database instance and click the instance ID.
In the left-side navigation pane, click Dashboard, then click the Exception Detection tab.
Specify a time range to view detection and prediction results for that period.
NoteThe end time must be later than the start time, and the interval cannot exceed seven days.
To monitor additional metrics, click More Metrics and select the metrics to include. For a full list of available metrics, see Metrics.
In the Exception Information section, find a metric that shows an anomaly, then click Diagnose in the Diagnose column.
In the Diagnostic Tree dialog box, review the overall performance of the database instance and identify the cause of the exception.

Metrics
DAS monitors the following metrics for anomaly detection and prediction.
| Metric | Description |
|---|---|
| tps | Transactions per second (TPS). |
| qps | Queries per second (QPS). |
| active_session | Number of active sessions. |
| delete_ps | Average number of DELETE statements executed per second. |
| insert_ps | Average number of INSERT statements executed per second. |
| update_ps | Average number of UPDATE statements executed per second. |
| select_ps | Average number of SELECT statements executed per second. |
| bytes_received | Average bytes received from all clients per second. |
| bytes_sent | Average bytes sent to all clients per second. |
| innodb_bp_hit | Read hit ratio of the InnoDB buffer pool. |
| innodb_data_written | Average bytes written to the InnoDB table per second. |
| innodb_data_read | Average bytes read from the InnoDB table per second. |
| mysql.innodb_log_writes | Average number of physical writes to the InnoDB redo log file per second. |
| innodb_rows_deleted | Average rows deleted from the InnoDB table per second. |
| innodb_rows_read | Average rows read from the InnoDB table per second. |
| innodb_rows_inserted | Average rows inserted into the InnoDB table per second. |
| innodb_rows_updated | Average rows updated in the InnoDB table per second. |
| mysql.mem_usage | Memory usage of the ApsaraDB RDS for MySQL instance in the entire operating system. |
| mysql.cpu_usage | CPU utilization of MySQL processes. The maximum value is 100% for Alibaba Cloud database instances. |