Introduction to TaurusDB Logs

TaurusDB supports the following types of logs:

• Error logs

  Error logs contain logs generated while a database is running, including error messages and slow SQL query statements. For details, see Managing Error Logs of a DB Instance.

• Slow query logs

  Slow query logs record statements that exceed the long_query_time value (10s by default). You are advised to set it to 1s. For details, see Managing Slow Query Logs of a DB Instance.

  You can use the following parameters to control TaurusDB logging:

  • log_queries_not_using_indexes: controls whether to record queries without indexes. The default value is OFF.
  • log_throttle_queries_not_using_indexes: limits the number of SQL statements without indexes per minute that can be written to the slow query log. The default value is 0.
• SQL Explorer

  Enabling SQL Explorer will allow TaurusDB to store all SQL statement logs for analysis.

  SQL Explorer cannot record all data. It has the following constraints:

  • Some data cannot be recorded if a buffer overrun occurs.
  • If the size of a SQL statement exceeds the value of rds_sql_tracer_max_record_size, the statement is not recorded by default.

  You can enable SQL Explorer on the DAS console.

• Audit logs

  If you enable the SQL audit function, all SQL operations will be logged for your download and query.

  By default, SQL audit is disabled. Enabling this function may affect database performance. For details, see Enabling SQL Audit.

• Binlogs

  Binlogs record all DDL and DML statements (except data query statements). You can download binlogs to a local PC for further analysis. Binlogs are stored in OBS buckets. For details, see Querying and Downloading Binlogs.