Database Audit currently supports TencentDB for MySQL 5.6, 5.7, and 5.8 (two-node and three-node) instances but not TencentDB for MySQL 5.5 or single-node instances. This document describes the billing of TencentDB for MySQL audit.
You need to pay for database audit only after it is enabled. For details, see [Enabling Database Audit] (https://www.tencentcloud.com/document/product/236/52086)
Database audit is billed by the stored log size for every clock-hour, and usage duration shorter than one hour will be calculated as one hour.
Region | Price (USD/GB/Hour) | |
---|---|---|
Frequent Access Storage | Infrequent Access Storage | |
China (including finance regions, Hong Kong, Macao, and Taiwan) | 0.00147059 | 0.00018382 |
Other countries and regions | 0.00220588 | 0.00027573 |
Frequent access storage represents an ultra-high-performance storage media with the best query performance. You can set the storage period, during which the audit data will be stored in the frequent access storage, but the data exceeding the period will be automatically transitioned to infrequent access storage. Different storages support the same audit capabilities with different performances.
You can set and modify the time period for frequent/infrequent access storage as needed, and the system will automatically move data between the frequent and infrequent access storage tiers based on the period, thus reducing your storage costs.
As shown in the picture, If the data of the last 7 days is set to be stored in frequent access storage, older data will be automatically transitioned to infrequent access storage. After the frequent access storage period is extended, the audit data that falls in the period will be automatically migrated from infrequent access storage to frequent access storage.
Frequent access storage throughput | Infrequent access storage throughput |
---|---|
110,000 SQLs/per second | 25,000 SQLs/per second |
After database audit is enabled for a pay-as-you-go/monthly subscribed TencentDB for MySQL instance, when you release an instance or an instance is released upon expiration, its corresponding audit service will also be stopped, and the logs will be automatically deleted and cannot be recovered.
Was this page helpful?