tencent cloud

TencentDB for MongoDB

Release Notes and Announcements
Release Notes
Announcements
User Guide
Product Introduction
Overview
Strengths
Use Cases
Cluster Architecture
Product Specifications
Features
Regions and AZs
Terms
Service Regions and Service Providers
Purchase Guide
Billing Overview
MongoDB Pricing
Billing Formula
Payment Overdue
Backup Space Billing
Configuration Adjustment Billing
Getting Started
Quickly Creating an Instance
Connecting to a TencentDB for MongoDB Instance
Reading/Writing Database
Operation Guide
Access Management
Instance Management
Node Management
Version Upgrade
Network Configuration
Monitoring
Backup and Rollback
Database Audit
Data Security
SSL Authentication
Log Management
Database Management
Multi-AZ Deployment
Disaster Recovery/Read-Only Instances
Parameter Configuration
Recycle Bin
Task Management
Performance Optimization
Data Migration Guide
Practical Tutorial
Optimizing Indexes to Break Through Read/Write Performance Bottlenecks
Troubleshooting Mongos Load Imbalance in Sharded Cluster
Considerations for Using Shard Clusters
Sample of Reading and Writing Data in MongoDB Instance
Methods for Importing and Exporting Data Based on CVM Connected with MongoDB
What to Do for Errors of Repeated Instance Creation and Deletion of Databases with the Same Names?
Troubleshooting MongoDB Connection Failures
Shard Removal Task: Guide for Confirming the Progress and Troubleshooting Issues
Performance Fine-Tuning
Ops and Development Guide
Development Specifications
Command Support in Sharded Cluster v3.2
Command Support in v3.6
Development Ops
Troubleshooting
Increased Slow Queries
Number of Connections Exceeding Limit
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Backup APIs
Account APIs
Other APIs
Task APIs
Introduction
Data Types
Error Codes
Instance Connection
Shell Connection Sample
PHP Connection Sample
Node.js Connection Sample
Java Connection Sample
Python Connection Sample
Python Read/Write Sample
Go Connection Sample
PHP Reconnection Sample
Product Performance
Test Environment
Test Method
Test Result
FAQs
Cost
Features
Sharded Cluster
Instance
Rollback and Backup
Connection
Data Migration
Others
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us

Viewing Audit Instances

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2025-07-15 16:46:00

Scenarios

TencentDB for MongoDB supports displaying instances with the audit feature enabled in the console in the form of a list, which makes it easy for you to quickly find audit instances by instance ID or instance name, and timely understand the audit rules of audit instances, as well as the storage size and retention period of audit logs.

Prerequisites

The Creating a TencentDB for MongoDB instance operation has been completed, and Database Audit has been enabled for the instance.
The status of the replica set instance or sharded instance of TencentDB for MongoDB is Running.

Directions

2. In the left sidebar, select MongoDB > Database Audit.
3. At the top of the Database Audit page on the right, select Region.
4. In the upper right corner of the audit instance list, select an instance with Audit Status being Enabled.
5. Click the search box to search the target instance in the drop-down list by Instance ID, Instance Name, Tag Key, or Tag.
6. View the audit information of the instance, as shown in the figure below.

Interface Parameter
Parameter Description
Instance ID/Name
The ID and name of the audit instance. Click the instance ID in blue font to redirect to the Audit Log page of the instance. For detailed information on audit log viewing, see Managing Audit Logs.
Version and Engine
The version information and storage engine of the audit instance. WT refers to the WiredTiger engine. For details, see Version and Storage Engine.
Audit Status
The audit status of the audit instance, displayed as enabled or disabled.
Log Retention Period
The retention period of the audit log. If modification is needed, see Modifying Retention Period of Audit Logs.
Stored Log Size
The storage size of the audit log, in MB. There may be a latency during data updates, and the final data in the billing system shall prevail. This data is only for reference.
Audit Rule
The audit rules of the instance, including: full audit and rule-based audit. If modification is needed, see Modifying Audit Rules.
Project
The name of the project to which the instance belongs.
Tag (key: value)
The key and value of the tag to which the audit instance belongs.

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백