Help Center/ TaurusDB/ User Guide/ Instance Management/ Instance Summary
Updated on 2026-08-19 GMT+08:00
View PDF
Share

Instance Summary

On the Basic Information page, you can get knowledge of the overall status of your TaurusDB instance, including alarms, intelligent anomaly diagnosis, and key performance metrics. Intelligent anomaly diagnosis uses operational data analytics and intelligent algorithms to assess instance health, and provides you with solutions and suggestions for handling detected exceptions.

Functions

Table 1 lists the functions provided on the Basic Information page.

Table 1 Function description

Function

Description

Instance Information

Shows basic information about your instance and allows you to modify the instance.

Active Alarms

Shows the active alarms of your instance, including alarms in the Alarm (metric) or Triggered (event) state.

Health Status

Shows the health status of your instance based on operational data analysis and intelligent algorithms.

Performance Monitoring

Shows the instance's key performance metrics, including the CPU usage, memory usage, number of slow SQL queries, and number of connections.

Storage and Backup

Shows the storage and backup usages of your instance. For yearly/monthly instances, you can scale up or down their storage and enable storage autoscaling.

Instance Summary

  1. Log in to the TaurusDB console.
  2. Click in the upper left corner and select a region.
  3. On the Instances page, click the target instance name to go to the Basic Information page.
  4. In the Instance Information area, check the instance information and modify the instance as required.

    Figure 1 Instance Information

In the Active Alarms area, check alarm information of your instance.

Based on the configured alarm rules, you can see information about your instance's active alarms, including alarms in the Alarm (metric) or Triggered (event) state.

Figure 2 Active Alarms

  • To check all alarm records, click All Alarms.
  • To configure alarm rules, click Alarm Settings to go to the Cloud Eye console.
  • To check active alarms over time, select a time window in the upper part of the Active Alarms area.

    The time window can be last 1 hour, last 6 hours, last 12 hours, last 24 hours, last 7 days, last 30 days, or a custom time period.

In the Health Status area, check the health diagnosis results of your instance. Table 2 provides the supported anomaly items and troubleshooting recommendations.

Table 2 Anomaly diagnostics reference

Diagnosis Item

Metric

Metric Description

Handling Suggestion

Reference

High vCPU utilization

CPU Usage (%)

CPU usage of the monitored object
  • Evaluate the SQL execution plan and add indexes to avoid full table scanning.
  • Upgrade vCPU specifications for compute-intensive workloads.

What Should I Do If the CPU Usage of My TaurusDB Instance Is High?

Memory bottleneck

Memory Usage (%)

Memory usage of the monitored object
  • Upgrade instance specifications.
  • Optimize SQL statements to reduce the use of temporary tables.
  • Reconnect sessions at a specific interval to release memory of the sessions.

How Do I Handle a Large Number of Temporary Tables Being Generated for Long Transactions and High Memory Usage?

High-frequency slow SQL

Slow Query Logs (Count/min)

Number of TaurusDB slow query logs generated per minute
  • Optimize slow SQL statements based on the execution plan.
  • Upgrade vCPUs.

How Do I Handle Slow SQL Queries Caused by Inappropriate Composite Index Settings?

Lock wait

Row Lock Time (ms)

Total time spent acquiring row locks for InnoDB tables
  • Metadata locks: Terminate sessions holding metadata locks to resume blocked operations.
  • InnoDB locks: Check for lock waits. Terminate the blocking sessions holding locks to resume blocked operations.

For details, see Managing Locks and Transactions.

What Should I Do If Locks on Long Transactions Block the Execution of Subsequent Transactions?

Row Lock Waits

Number of times that operations on InnoDB tables had to wait for a row lock

The system performs diagnostics on instances by combining runtime data with intelligent algorithms and provides diagnosis results and optimization recommendations for detected anomalies.

Figure 3 Diagnosis results

You can also click Handle Now of an abnormal item to view its diagnosis details and choose handling suggestions as needed.

  • Handling real-time sessions and corresponding SQL statements
    • Analyze root causes (OBT).

      Click Root Cause Analysis in the Operation column. The displayed dialog box shows details about blocked sessions and their root cause SQL statements.

    • Manually kill sessions.

      To end a single session, click Kill Session in the Operation column to restore the database. You can also select sessions and click Kill Session above the list to kill them in batches. You can select up to 50 sessions at a time.

    For details, see Managing Real-Time Sessions.

    Figure 4 Handling sessions

  • Handling slow SQL queries
    • Export slow query log details.

      Click Export. In the displayed dialog box, select an export mode. Quick export and full export are supported. After the slow query log details are exported, click View All Export Records. In the displayed dialog box, click Download in the Operation column. After the download is complete, view the slow query log details in the ZIP package.

    • Throttle SQL statements.

      To add a SQL throttling rule, click SQL Throttling in the Operation column. In the displayed dialog box, specify SQL Type, Keyword, and Max. Concurrent Requests, and click OK. For details, see Configuring SQL Throttling.

    • Perform SQL diagnosis.

      Choose More > Diagnose in the Operation column. In the displayed dialog box, confirm slow SQL query information and click OK to start the diagnosis. In the displayed dialog box, view the SQL diagnosis results.

    • Check historical execution plans.

      Choose More > Historical Execution Plan in the Operation column to view the SQL execution plan summary.

    For details, see Viewing Slow Query Log Details.

    Figure 5 Handling slow SQL queries

  • Increasing specifications

    Go to the page for changing instance specifications. For details, see Changing the vCPUs and Memory of a DB Instance or Node Manually.

In the Performance Monitoring area, you can view the vCPUs (used/total), memory (used/total), slow SQL queries, and connections of your instance.

Figure 6 Performance Monitoring

  • To check all metrics, click Real-Time Monitoring to go to the DBA Assistant page. For details, see Viewing Real-Time Performance Metrics.
  • To check the analysis results of slow queries, click Slow SQL Log to go to the DBA Assistant page. For details, see Viewing Slow SQL Query Logs.
  • To check metric changes over time, select a time range in the upper part.

    The time window can be last 1 hour, last 6 hours, last 12 hours, last 24 hours, last 7 days, last 30 days, or a custom time period.

This area shows the storage and backup space usages of your instance. For yearly/monthly instances, you can scale up or down their storage and enable storage autoscaling.

Figure 7 Storage and Backup

  • Files that occupy the storage space include data files, log files, and other temporary files. To check the distribution and changes of used storage, see Managing Storage.
  • For yearly/monthly instances, the initially requested storage may not always match actual consumption as your data volumes change. TaurusDB lets you scale up or down storage capacity to suit your needs. For details, see Changing the Storage Space of a DB Instance Manually.
  • TaurusDB backups are stored on OBS. They do not occupy the storage of your instance. TaurusDB provides free backup space of the same size as your purchased storage. If the free space TaurusDB provides is used up, the additional space required will be billed. For details about backup pricing, see How Is TaurusDB Backup Data Billed?
Parent Topic: Instance Management