Database Autonomy Service:Slow query logs

Video introduction

Procedure

1. Log on to the DAS console.

2. In the navigation pane on the left, click Intelligent O&M Center > Instance Monitoring .

3. Find the target instance and click the instance ID to open the instance details page.

4. In the navigation pane on the left, click Request Analysis > Slow Logs.

5. Select a time range to view the Slow Log Trend, Event Distribution, Slow Log Statistics, and Slow Log Details.

   Note

   The end time must be later than the start time. The maximum time range is seven days. You can query slow query logs that were generated in the last month.

   • In the Slow Query Log Trends chart, you can select a point in time to view the corresponding Slow Query Log Statistics, and Slow Query Log Details.

     Note

     If a slow SQL statement is too long to be fully displayed, you can hover the pointer over the statement. The complete statement appears in a dialog box.

   • For sharded cluster instances, you can view the number of slow requests for each node in the Node ID drop-down list area.

   • Click to save the slow log information locally.

   • Click to go to OpenAPI Explorer and debug the API with the parameters that you selected.

   • In the Event Distribution section:

     You can query slow log events within the specified time range. Click an event to view its details.

   • In the Slow Log Statistics area, find the target log template. In the Actions column, click the Details button to view the Slow Log Sample .

   • In the Slow Log Statistics area, find the target log template. In the Actions column, click the Optimize button. In the Optimize dialog box that appears, view the diagnosis results.

     Note

     This optimization feature, which mainly provides index optimization suggestions, is available only for slow query log scenarios where the Operation Type is query. The supported scope is as follows:

     Supported scenarios:

     • Field-specific search: If a query such as db.col.find({ a: 1 }) is recorded in the slow query log, the system recommends that you create a corresponding index: db.col.createIndex({ a: 1 }).

     • Compound query: If a query such as db.col.find({ a: 1, b: 1 }) is recorded in the slow query log, we recommend that you create a compound index, such as db.col.createIndex({ a: 1, b: 1 }).

     Unsupported scenarios:

     • Existing indexes are not recommended again.

     • Special index types such as text, unique, or hash are not supported.

     • Queries do not support complex logical operators, such as $or or $and.

     • Index suggestions are generated only for find operations, not for other operations such as sorting $sort or collation $collation.

     If you accept the diagnostic suggestion, click Copy in the upper-right corner of the page, and paste the optimized statement into a database client or DMS to execute it. If you do not accept the diagnostic suggestion, you can click Cancel to end the diagnosis.

     Important

     Adding an index might degrade the execution plans of other queries and consume resources such as instance performance and storage space. Before you accept a suggestion, assess the potential risks and impacts on other queries and overall resource consumption.

FAQ