From da2daba4fce527cc7de161eb30b29ba21e051960 Mon Sep 17 00:00:00 2001 From: wangdengke2 Date: Fri, 22 May 2026 12:04:54 +0000 Subject: [PATCH] taurusdb_umn Reviewed-by: Wagner, Fabian Co-authored-by: wangdengke2 Co-committed-by: wangdengke2 --- docs/taurusdb/umn/en-us_topic_0000002521462469.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/taurusdb/umn/en-us_topic_0000002521462469.html b/docs/taurusdb/umn/en-us_topic_0000002521462469.html index b9473cf91..c9ce918f4 100644 --- a/docs/taurusdb/umn/en-us_topic_0000002521462469.html +++ b/docs/taurusdb/umn/en-us_topic_0000002521462469.html @@ -18,9 +18,9 @@ -

Constraints

Collecting abnormal snapshots will cause about 5% of instance performance loss.

+

Constraints

Collecting anomaly snapshots will cause about 5% of instance performance loss.

-

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and project.
  3. Click in the upper left corner of the page and choose Databases > TaurusDB.
  4. On the Instances page, click the instance name.
  5. In the navigation pane, choose DBA Assistant > Historical Diagnosis.
  6. Click Anomaly Snapshots.
  7. Click on the right of Collect Abnormal Snapshots to enable anomaly diagnosis.

    After anomaly diagnosis is enabled, if any anomaly listed in Table 1 occurs, you can view its snapshots. Anomaly snapshot records are retained for seven days and will be deleted after this time expires. A maximum of 100 records can be retained for a single node.

    +

    Procedure

    1. Log in to the management console.
    2. Click in the upper left corner and select a region and project.
    3. Click in the upper left corner of the page and choose Databases > TaurusDB.
    4. On the Instances page, click the instance name.
    5. In the navigation pane, choose DBA Assistant > Historical Diagnosis.
    6. Click Anomaly Snapshots.
    7. Click on the right of Anomaly Collection to enable anomaly diagnosis.

      After anomaly diagnosis is enabled, if any anomaly listed in Table 1 occurs, you can view its snapshots. Anomaly snapshot records are retained for seven days and will be deleted after this time expires. A maximum of 100 records can be retained for a single node.

      Click Diagnosis Details in the Operation column to view diagnosis result details and optimization suggestions.

      Click the Anomaly Snapshots tab to view session snapshots, metadata lock snapshots, InnoDB lock snapshots, and transaction snapshots.