Help Center/ TaurusDB/ User Guide/ DBA Assistant/ Performance Monitoring/ Viewing the Overall Status of a DB Instance

Updated on 2025-08-21 GMT+08:00

View PDF

Viewing the Overall Status of a DB Instance

The Dashboard page allows you to view the overall status of the current DB instance, including alarms, health check results, compute resource usage, storage resource usage, and key performance metrics.

Viewing the Overall Status of a DB Instance

Log in to the management console.
Click in the upper left corner and select a region and project.
Click in the upper left corner of the page and choose Databases > TaurusDB.
On the Instances page, click the instance name.
In the navigation pane, choose DBA Assistant > Real-Time Diagnosis.
On the Dashboard page, view instance alarms provided by Cloud Eye.

You can customize alarm rules by adjusting alarm policies and severities for key metrics, such as CPU usage and disk usage. To view alarm details, click the number next to an alarm severity.

Figure 1 Alarms

Figure 2 Alarm list

In the Health area, you can view real-time health check results. By default, the data for high vCPU utilization, memory bottlenecks, high-frequency slow SQL statements, and lock waits are displayed.

For abnormal metrics, click Diagnose to view diagnosis details and suggestions. For details, see Table 1.

For details about metrics, see Viewing TaurusDB Metrics. For details about how to configure alarm rules on Cloud Eye, see Configuring TaurusDB Alarm Rules.

Figure 3 Health
Click to enlarge

**Table 1** Health diagnosis and suggestions
Item	Exception Trigger Condition	Suggestion
High vCPU utilization	Either of the following conditions is met: After you configure alarm rules on Cloud Eye, an alarm is reported, indicating the CPU usage is high. The CPU usage exceeds 95% for more than 2.5 minutes of a 5-minute measurement period.	What Should I Do If the CPU Usage of My TaurusDB Instance Is High?
Memory bottleneck	Either of the following conditions is met: After you configure alarm rules on Cloud Eye, an alarm is reported, indicating the memory usage is high. The memory usage exceeds 95% within a 5-minute measurement period.	How Do I Handle a Large Number of Temporary Tables Being Generated for Long Transactions and High Memory Usage?
High-frequency slow SQL	Either of the following conditions is met: After you configure alarm rules on Cloud Eye, an alarm is reported, indicating there are too many slow logs. There are more than 100 slow logs within five minutes.	How Do I Handle Slow SQL Statements Caused by Inappropriate Composite Index Settings?
Lock wait	After you configure alarm rules on Cloud Eye, any of the following alarms is reported: Row Lock Time InnoDB Row Locks Row Lock Waits	What Should I Do If Locks on Long Transactions Block the Execution of Subsequent Transactions?

In the Compute Resource Usage area, the vCPU usage and memory usage are displayed by default. The displayed values are the average values for 5-minute measurement periods.

Figure 4 Compute Resource Usage
Click to enlarge

In the Storage Resource Usage area, the storage usage, disk read IOPS, and disk write IOPS are displayed by default. The displayed values are the average values for 5-minute measurement periods.

Figure 5 Storage Resource Usage
Click to enlarge

In the Key Performance Metrics area, the CPU usage & slow query logs, connections, memory utilization, and disk reads/writes from the last hour are displayed by default. The displayed values are real-time values.

Figure 6 Key Performance Metrics
Click to enlarge