All Products
Search
Document Center

Database Autonomy Service:Monitoring dashboards

Last Updated:Mar 28, 2026

When you manage multiple database instances, switching between individual instance pages to compare performance metrics is slow and error-prone. Database Autonomy Service (DAS) monitoring dashboards give you a single view to track metrics across instances side by side, correlate anomalies across different metrics at the same time point, and drill into specific charts without leaving the dashboard.

Prerequisites

Before you begin, ensure that you have:

Create a monitoring dashboard

  1. Log on to the DAS console.

  2. In the left-side navigation pane, choose Intelligent O&M Center > Monitoring Dashboard.

  3. On the Custom Dashboard page, click a tab to select a database engine.

  4. On the tab for the specified database engine, click Add Monitoring Dashboard.

  5. In the Create Monitoring Dashboard dialog box, set Dashboard Name and click OK.

  6. Click Select Metrics and Instances. In the Select Metrics and Instances dialog box, select the instances and metrics to monitor, then click .

    You can select up to 32 instances at a time. For available metrics, see Metrics.

  7. Click Confirm.

To update the instances or metrics in an existing dashboard, click Add Instances and Metrics.

View metric trends

  1. Log on to the DAS console.

  2. In the left-side navigation pane, choose Intelligent O&M Center > Monitoring Dashboard.

  3. On the Custom Dashboard page, click a tab to select a database engine.

  4. Select the monitoring dashboard and specify a time range. Time range constraints:

    • The end time must be later than the start time.

    • The interval cannot exceed seven days.

    • For Tair (Redis OSS-compatible) instances, the interval cannot exceed three hours.

Once the dashboard loads, use the following controls to explore your data:

ControlDescription
Filter by InstanceSelect specific instances to compare their metrics in the same view
Auto Refresh (Every 5Seconds)Refresh all metric trend charts every five seconds
Linkage ChartEnable multi-metric linkage to view values of different metrics at the same time point
Chart LayoutSet the number of metric trend charts displayed per row
Add Instances and MetricsModify the instances and metrics in the dashboard
Details (in a trend chart)Zoom in on a chart and adjust the time range for that metric
Delete (in a trend chart)Remove a metric from the dashboard
Tip: Click the Question mark icon icon to the right of a metric to view its description.

Metrics

The following tables list the available metrics for each supported database engine.

ApsaraDB RDS for MySQL and self-managed MySQL

CategoryMetricDescription
MySQL ServertpsTransactions per second (TPS)
qpsQueries per second (QPS)
active_sessionNumber of active sessions
total_sessionTotal number of sessions
delete_psAverage DELETE statements per second
insert_psAverage INSERT statements per second
replace_psAverage REPLACE statements per second
update_psAverage UPDATE statements per second
select_psAverage SELECT statements per second
bytes_receivedAverage bytes received from all clients per second
bytes_sentAverage bytes sent to all clients per second
iops_usageI/O operations per second (IOPS) usage
InnoDB storage engineinnodb_bp_hitRead cache hit ratio of the InnoDB buffer pool
innodb_bp_dirty_pctRatio of dirty pages in the InnoDB buffer pool
innodb_bp_usage_pctUtilization of the InnoDB buffer pool
innodb_data_writtenAverage bytes written to the InnoDB table per second
innodb_data_readAverage bytes read from the InnoDB table per second
innodb_rows_deletedAverage rows deleted from the InnoDB table per second
innodb_rows_readAverage rows read from the InnoDB table per second
innodb_rows_insertedAverage rows inserted into the InnoDB table per second
innodb_rows_updatedAverage rows updated in the InnoDB table per second
MySQL processcpu_usageCPU utilization of the MySQL process. The maximum value is 100% for Alibaba Cloud database instances.
mem_usageMemory usage of the MySQL database within the operating system
iopsIOPS of the MySQL database
disk_usageDisk usage

Tair (Redis OSS-compatible) and self-managed Redis

CategoryMetricDescription
Databaseinstantaneous_ops_per_secCommands processed per second
get_qpsRead requests per second
put_qpsWrite requests per second
connection_usageConnection usage
inflowData read from the database over the network per second
outflowData written to the database over the network per second
used_memoryTotal bytes that Redis allocates via its allocator
mem_usageMemory usage
Redisavg_rtAverage response time of Redis
max_rtMaximum response time of Redis
proxy.avg_rtAverage response time of the Redis proxy node
proxy.max_rtMaximum response time of the Redis proxy node
proxy.connection_usageConnection usage of the Redis proxy
cpu_usageCPU utilization of the Redis process
Keysevicted_keysKeys evicted due to the maximum memory limit
total_keysTotal number of keys in the database
expired_keysTotal number of key expiration events
Redis KeyshitNumber of hit keys
missNumber of missed keys

ApsaraDB for MongoDB and self-managed MongoDB

CategoryMetricDescription
MongoDBopcounters.insertINSERT statements per second
opcounters.queryQUERY statements per second
opcounters.updateUPDATE statements per second
opcounters.deleteDELETE statements per second
opcounters.commandCOMMAND statements per second
opcounters.getmoreGETMORE statements per second
connections.currentNumber of active sessions
metrics.cursor.open.totalNumber of open cursors
metrics.cursor.timedOutNumber of timeout cursors
network.bytesInBytes written to MongoDB per second
network.bytesOutBytes read from MongoDB per second
network.numRequestsRequests sent to MongoDB per second
MongoDB processcpu_usageCPU utilization of the MongoDB process
mem_usageMemory usage of the MongoDB process
disk_usageDisk usage of the MongoDB process

ApsaraDB RDS for PostgreSQL

CategoryMetricDescription
Hostcpu_sys_ratioCPU utilization of the PostgreSQL process in kernel state
cpu_user_ratioCPU utilization of the PostgreSQL process in user state
cpu_usageCPU utilization of the PostgreSQL process
mem_usageMemory usage of the PostgreSQL process
data.r_sRead IOPS of the disk on which the data directory resides
data.iopsIOPS of the disk on which the data directory resides
data.w_sWrite IOPS of the disk on which the data directory resides
local_fs_size_totalTotal disk space of the host
data.fs.usedUsed space of the disk on which the data directory resides
data.fs.usageSpace usage of the disk on which the data directory resides
network_out_ioOutbound network traffic of the PostgreSQL process
network_ioNetwork traffic of the PostgreSQL process
network_in_ioInbound network traffic of the PostgreSQL process
PostgreSQL basic monitoringwaiting_connectionNumber of pending connections
idle_in_transactionNumber of idle sessions
active_sessionNumber of active connections
total_sessionTotal number of current connections
tup_insertedRecords inserted per second
tup_deletedRecords deleted per second
tup_updatedRecords updated per second
tup_returnedRecords returned per second for full table scans
tup_fetchedRecords returned per second for index scans
tpsTPS in PostgreSQL
xact_rollbackTransactions rolled back per second
xact_commitTransactions committed per second
deadlocksDeadlocks per second
oldest_snapshotPoint in time before which dead tuples can be recycled by the instance
max_sent_delayReplication latency from the secondary ApsaraDB RDS for PostgreSQL instance
max_replay_delayLatency at which the secondary instance replays transaction commits
long_query_5sSQL statements with execution duration >= 5 seconds
long_query_1sSQL statements with execution duration >= 1 second
long_query_3sSQL statements with execution duration >= 3 seconds
long_idle_in_transaction_3sTransactions idle for 3 seconds or longer
long_idle_in_transaction_5sTransactions idle for 5 seconds or longer
long_idle_in_transaction_1sTransactions idle for 1 second or longer
long_2pc_1sTwo-phase commit (2PC) transactions lasting 1 second or longer
long_2pc_5s2PC transactions lasting 5 seconds or longer
long_2pc_3s2PC transactions lasting 3 seconds or longer

ApsaraDB RDS for SQL Server

CategoryMetricDescription
SQL Server processcpu_usageCPU utilization within the operating system
db_ioI/O requests per second
db_io_readRead I/O requests per second
db_io_writeWrite I/O requests per second
other_sizeDisk space occupied by system files
log_sizeDisk space occupied by log files
tmp_sizeDisk space occupied by temporary files
ins_sizeTotal disk space occupied by the instance
data_sizeDisk space occupied by data files
DatabaseqpsAverage SQL statements executed per second
connection_resetTotal logon attempts from the connection pool per second
active_temp_tablesNumber of active temporary tables
active_sessionNumber of active threads
active_cursorsNumber of active cursors
sessionsTotal number of connections
active_transactionsNumber of active transactions
transactionsAverage transactions per second
write_transactionsAverage write transactions per second
read_kbAverage outbound traffic per second
write_kbAverage inbound traffic per second
Basic monitoringcache_hit_ratioHit ratio of the high-speed cache
bufferpoolPercentage of pages found in the high-speed cache out of all pages read from disk
fullscansAverage full table scans per second
autoparam_attempts_per_secAuto parameterization attempts per second
forced_parameterizations_per_secSuccessful forced parameterizations per second
sql_compilationsSQL compilations per second
unsafe_autoparams_per_secUnsafe auto parameterization attempts per second
failed_autoparams_per_secAuto parameterization failures per second
safe_autoparams_per_secSafe auto parameterization attempts per second
resqlcompilationsSQL statement recompilations per second
lazy_writesDirty pages written to disk per second
checkpointDirty pages the checkpoint operation must write per second
logoutLogouts per second
loginsLogons per second
locktimeoutLock requests that time out per second, including NOWAIT locks
deadlockLock requests resulting in a deadlock per second
lock_requests_per_secNew locks and lock conversions per second
lockwaitsLock requests the client waits for per second
lock_waitsStatistics of processes waiting for locks
latchwaitsLatch requests not immediately granted per second
lock_wait_time_msAverage wait time per lock request that results in a wait
average_latch_wait_timeAverage wait time to request a latch resource
table_lock_escalations_per_secTimes a lock on a table is escalated to the HoBT level or table level
average_lock_wait_timeAverage wait time of the requested lock resource
total_latch_wait_timeTotal wait time for locks in the last second

PolarDB for MySQL clusters

CategoryMetricDescription
Databasecom_deleteAverage DELETE statements per second
com_insertAverage INSERT statements per second
com_replaceAverage REPLACE statements per second
com_selectAverage SELECT statements per second
com_updateAverage UPDATE statements per second
qpsQPS of the PolarDB for MySQL cluster
tpsTPS of the PolarDB for MySQL cluster
PolarDB processcpu_usageCPU utilization of the PolarDB process. The value 200% indicates that two CPU cores are in use.
mem_usageMemory usage within the operating system
PolarDB Serveractive_sessionNumber of active sessions
total_sessionTotal number of sessions
output_trafficAverage bytes sent to all clients per second
input_trafficAverage bytes received from all clients per second
InnoDB storage engineinnodb_data_readAverage bytes read from the InnoDB table per second
innodb_data_writtenAverage bytes written to the InnoDB table per second
innodb_buffer_dirty_ratioRatio of dirty pages in the InnoDB buffer pool
innodb_buffer_read_hitRead cache hit ratio of the InnoDB buffer pool
innodb_buffer_use_ratioUtilization of the InnoDB buffer pool
innodb_rows_deletedAverage rows deleted from the InnoDB table per second
innodb_rows_insertedAverage rows inserted into the InnoDB table per second
innodb_rows_readAverage rows read from the InnoDB table per second
innodb_rows_updatedAverage rows updated in the InnoDB table per second