Managing Anomaly Snapshots

Scenarios

This function intelligently detects instance anomalies and records information about session, lock, and transaction snapshots to facilitate subsequent fault locating.

Constraints

• Enabling anomaly collection will cause about 5% of instance performance loss.
• Each anomaly snapshot can be retained for a maximum of seven days. A maximum of 10 anomaly snapshots can be retained for each node at the same time.
• Anomaly snapshots record long-running transactions.

Enabling Anomaly Collection

1. Log in to the DAS console.
2. Click in the upper left corner and select a region and project.
3. Click in the upper left corner, and under Databases, click Data Admin Service.
4. In the navigation pane, choose Intelligent O&M > Instance List.
5. In the upper right corner of the Instance List page, search for instances by engine type, instance name, or instance IP.
6. Locate the target instance and click Details.
7. Click the Anomaly Snapshots tab.
8. On the displayed page, toggle on the Anomaly Collection switch.

Viewing Anomaly Snapshots

1. Click the Anomaly Snapshots tab.
2. On the displayed page, view session snapshots, metadata lock snapshots, InnoDB lock snapshots, and transaction snapshots of the DB instance.
   • To view anomaly causes, click Diagnosis Details in the Operation column.
   • To view details about slow SQL statements, click Slow SQL in the Operation column.