Note:The audit log display time is down to milliseconds, facilitating more precise sorting and problem analysis of SQL commands.
Note:You can select any time period with data for search. Up to the first 60,000 eligible records can be displayed.
Note:When filtering by SQL command, the symbol
*
does not represent a fuzzy match. All SQL command searches are fuzzy searches.
SELECT
commands.The following fields are supported in TencentDB for MySQL and TDSQL-C for MySQL audit logs. You can click the following icon on the Audit Log tab in the TencentDB for MySQL or TDSQL-C for MySQL console to get and view the complete SQL audit logs.
No. | Field Name | Description | Remarks |
---|---|---|---|
1 | host | Client IP | - |
2 | dbname | Database name | - |
3 | user | Username | - |
4 | sql | SQL statement | - |
5 | sqlType | SQL statement type | - |
6 | errCode | Error code | 0 indicates success |
7 | affectRows | Number of affected rows | - |
8 | checkRows | Number of scanned rows | - |
9 | sentRows | Number of returned rows | - |
10 | threadId | Thread ID | - |
11 | ruleNum | Audit rule ID | - |
12 | policyName | Audit policy name | - |
13 | instanceName | Instance name | - |
14 | timestamp | Start time (s) | - |
15 | nsTime | Start Time (ns), which forms the start time accurate down to the nanosecond together with timestamp |
Example: timestamp.nsTime 1577953020.887984015 |
16 | execTime | Execution time (ms) | - |
17 | cpuTime | CPU time (μs) | - |
18 | lockWaitTime | Lock wait time (μs) | - |
19 | ioWaitTime | IO wait time (μs) | - |
20 | trxLivingTime | Transaction execution time (μs) | - |
Was this page helpful?