All Products
Search

This Product

    Database Autonomy Service:Announcement: MongoDB audit log feature upgrade and management changes

    Document Center

    Database Autonomy Service:Announcement: MongoDB audit log feature upgrade and management changes

    Last Updated:Feb 04, 2026

    To provide more flexible audit log storage and management capabilities, we are upgrading the audit log feature for ApsaraDB for MongoDB. This upgrade introduces a new version of audit logs that supports hot-cold tiered storage and adjusts the instance activation process and OpenAPI management methods.

    Effective date

    00:00:00 on February 1, 2026 (Singapore Time). This change will be rolled out gradually by region.

    Details

    New features

    The new version of audit logs provides the following core capabilities:

    • Hot-cold tiered storage: Optimizes storage costs and query performance.

    • Per-instance retention configuration: Allows you to independently configure audit log retention periods for individual MongoDB instances.

    • Instance-level billing: Itemizes costs by instance billing items to facilitate resource attribution and cost management.

    Version rules

    After the upgrade, audit log activation and version management will follow these rules:

    Instance status

    Version rule

    Instances that have never enabled audit logs

    Only the new version can be activated through the new audit log page.

    Instances with the legacy version of audit logs enabled

    You can continue to use the legacy version. Features and billing remain unchanged.

    Instances where the legacy version of audit logs has been disabled

    The legacy version cannot be re-enabled. Only the new version can be activated.

    OpenAPI adjustments

    The OpenAPIs used to manage new and legacy audit logs are defined as follows

    New version

    • Recommended method: Use the Database Autonomy Service (DAS) OpenAPI for complete feature support and optimal long-term compatibility.

    • MongoDB OpenAPI compatibility: Some existing ApsaraDB for MongoDB OpenAPIs remain partially compatible with the new audit log version, as detailed below.

      MongoDB OpenAPI

      Compatibility

      Notes

      ModifyAuditPolicy

      New & Legacy

      After you disable the legacy version, this API can only enable the new version and cannot re-enable the legacy version.

      ModifyAuditLogFilter

      New & Legacy

      —

      DescribeAuditLogFilter

      New & Legacy

      —

      DescribeAuditPolicy

      New & Legacy

      —

      DescribeMongoDBLogConfig

      New & Legacy

      —

      DescribeAuditRecords

      Legacy only

      This API does not support querying new version audit log records.

    Legacy version

    Legacy version audit logs continue to be managed through existing ApsaraDB for MongoDB OpenAPIs.

    Impacts

    Console operations

    Once legacy audit logs are disabled, they cannot be re-enabled. Only the new version will be available for activation in the console.

    API and automation

    Automation scripts or tools that rely on OpenAPI for audit log management must be adapted after target instances switch to the new version of audit logs. You must switch to using DAS OpenAPIs for operations. Legacy MongoDB OpenAPIs provide only limited support for new-version audit logs and cannot be used for full lifecycle management.

    Recommendations

    1. All users who use MongoDB OpenAPIs to manage audit logs should evaluate the impact of this change on your automated O&M processes in advance and plan the corresponding API invocation switching strategy.

    2. To use the OpenAPI for the new audit log, see the API Overview of Database Autonomy Service.