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 @@ -
Collecting abnormal snapshots will cause about 5% of instance performance loss.
+Collecting anomaly snapshots will cause about 5% of instance performance loss.
in the upper left corner and select a region and project.
in the upper left corner of the page and choose Databases > TaurusDB.
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.
+
in the upper left corner and select a region and project.
in the upper left corner of the page and choose Databases > TaurusDB.
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.