Modify the retention period for audit logs

Precautions

• The specified retention period is valid for all instances in the region of the current instance. We recommend that you evaluate the retention period of audit logs for all instances in the same region before you set the parameter.
• Audit logs are billed on a pay-as-you-go basis based on the storage usage and log retention period. To prevent high costs, we recommend that you set the shortest period that meets your business requirements.

Procedure

1. Log on to the ApsaraDB for MongoDB console.
2. In the upper-left corner of the page, select the resource group and region to which the instance belongs.
3. In the left-side navigation pane, click Replica Set Instances or Sharded Cluster Instances based on the instance type.
4. Click the ID of an instance, or click in the Actions column corresponding to the instance and select Manage.
5. In the left-side navigation pane of the instance details page, choose Data Security > Audit Logs.
6. In the upper-right corner, click Service Settings.
7. In the Global Settings section of the Service Settings panel, modify the log retention period.
   Notice

   • The specified retention period is valid for all instances in the region of the current instance. We recommend that you evaluate the retention period of audit logs for all instances in the same region before you set the parameter.
   • Audit logs are billed on a pay-as-you-go basis based on the storage usage and log retention period. To prevent high costs, we recommend that you set the shortest period that meets your business requirements.
8. Click OK.

Related API operations