Slow query logs impair the stability of databases. When databases suffer issues such as high workloads and performance jitter, the administrator or developer first checks whether slow query logs are being collected.
Common methods to view slow query logs
- Directly view the logs
- Slow query logs are not easy to read because they are not parameterized, aggregated, or sampled.
- Existing issues cannot be quickly located or fixed.
- View the logs by using self-managed slow query log platforms
- Self-managed log collection, computing, and storage platforms incur high costs.
- Platform development and O&M personnel are required.
Slow query log analysis feature of DAS
DAS provides the slow query log analysis feature. You can view the trends, statistics, and details of slow query logs in the DAS console.
- Easy operation: For more information about how to use the slow query log analysis feature, see Analyze slow query logs and Slow query log analysis.
- Low costs: Self-managed log collection, computing, and storage platforms are not required. This helps you save costs.
- Closed-loop management: Slow query logs are managed throughout their entire lifecycle, including discovery, analysis, diagnosis, optimization, and tracking.
- Low requirements: Professional data administrators are not required.