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 management console.
2. Click in the upper left corner of the page and choose Databases > Relational Database Service.
3. On the Instances page, click the DB instance name.
4. In the navigation pane, choose DBA Assistant > Historical Diagnosis.
5. Click the Anomaly Snapshots tab.
6. 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. For details, see Viewing Slow Query Logs of a DB Instance.