long_query_time parameter are recorded in the slow logs.long_query_time: This is the slow query threshold parameter, which supports microsecond-level precision and defaults to 1s. SQL statements with an execution time exceeding this value are recorded in the slow log. The parameter can be manually adjusted by users, with a valid range of 0.000000 to 3600.00000. To adjust the parameter, see Setting Instance Parameters.Operation Item | Scenarios | How it Works |
Configure slow log related parameters. | Record slow logs by configuring the value of the long_query_time parameter. | |
Query and Download Slow Log Details. | On the slow log details page, SQL statements with an execution time exceeding 1 second in the database within the last 7 days are recorded by default. You can query slow log information, which includes: execution time, SQL statement, client address, username, database name, execution duration (seconds), lock duration (seconds), rows examined, rows returned, RPC call duration (RpcTime), storage RPC duration (StorageRpcTime), storage lock wait duration (TDStoreLockTime), RPC retry wait duration (RpcRetryDelayTime), RPC access details (RpcTrace), and execution plan (Explain). Download is also supported. | |
Slow Log Delivery | Slow logs can be delivered to CLS (Cloud Log Service) for analysis, enabling rapid monitoring and pinpointing of business issues. | |
Analyzing and Optimizing Slow Logs. | You can view complete SQL templates, SQL samples, and optimization suggestions and descriptions through DBbrain to analyze and optimize SQL. | - |
Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
masukan