tencent cloud

TencentDB for MySQL

Tutorial Pengguna
Pengenalan Produk
Ikhtisar
Keunggulan
Kasus Penggunaan
Database Architecture
Kebijakan Isolasi Sumber Daya
Database Instance
Ketersediaan Tinggi (Beberapa AZ)
Wilayah dan AZ
Panduan Pembelian
Ikhtisar Penagihan
Metode Pembelian
Pembayaran Jatuh Tempo
Pengembalian Dana
Biaya Penyesuaian Instans
Penagihan Ruang Cadangan
Memulai
Ikhtisar
Membuat Instans MySQL
Panduan Operasi
Batas Penggunaan
Ikhtisar Operasi
Manajemen dan Pemeliharaan Instans
Peningkatan Versi
Memperluas Instans
Proksi Database
Manajemen Akun
Konfigurasi Parameter
Pencadangan dan Pengembalian
Migrasi data
Jaringan dan Keamanan
Pemantauan dan Alarm
Pusat Log
Tag
Laporan Resmi
Laporan Resmi Keamanan
Service Agreement
Service Level Agreement
Terms of Service
DokumentasiTencentDB for MySQL

Database Audit Billing Overview

Mode fokus
Ukuran font
Terakhir diperbarui: 2026-03-20 17:21:29
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/Infrequent Access Storage

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.

Frequent/Infrequent storage architecture


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.

Performance differences between frequent and infrequent access storage

Frequent access storage throughput
Infrequent access storage throughput
110,000 SQLs/per second
25,000 SQLs/per second

Release Description

After database audit is enabled for a pay-as-you-go/yearly/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.

Overdue Payments

1. When your account balance becomes negative:
You can continue to use your database audit for 2 hours from the moment your account becomes negative. We will also continue to bill you for this period.
When your account has overdue payments for two hours, the database audit service will be automatically stopped, and the billing will stop.
2. After the service is automatically stopped:
If you top up your account to a positive balance within 24 hours after the database audit is automatically stopped, it will be resumed, and the billing will continue; otherwise, it cannot be resumed.
If your account balance remains negative after 24 hours, the logs will be deleted and cannot be recovered.

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan