Configuring SQL Explorer for a DB Instance
Scenarios
Enabling SQL Explorer will allow TaurusDB to store SQL statement logs for analysis.
You can enable SQL Explorer on the DAS console.
Constraints
- SQL Explorer does not guarantee that all data is recorded. The following limitations apply:
- SQL Explorer is subject to in-memory buffer limits. Under heavy workloads, there is a small chance that some records may be dropped when the buffer is full.
- By default, a SQL Explorer record is dropped if its size exceeds the configured limit.
You can use the rds_sql_tracer_max_record_size parameter to configure whether oversized records are dropped. To set this parameter, see Modifying Instance Parameters.
- If the instance kernel version is 2.0.81.260900 or later, you can modify the rds_sql_tracer_truncate_query parameter to control whether SQL statements that exceed the length limit are truncated and retained. The original SQL statement will be incomplete after truncation.
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot