Filter MongoDB Audit Log Types via ModifyAuditLogFilter API - ApsaraDB for MongoDB - Alibaba Cloud - ApsaraDB for MongoDB

Operation description

The instance must be in the Running instance status when you invoke this operation.
This operation is limited to 30 calls per minute. If this limit is exceeded, the calls are throttled. Do not invoke this operation at a high frequency. If you require high-frequency calls, use a Logstore. For details, see Manage a Logstore.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

dds:ModifyAuditLogFilter

update

*dbinstance

acs:dds:{#regionId}:{#accountId}:dbinstance/{#dbinstanceId}

None

Request parameters

Parameter	Type	Required	Description	Example
DBInstanceId	string	Yes	The instance ID.	dds-bp12c5b040dc****
Filter	string	Yes	The collection types of audit logs. Separate multiple collection types with commas (,). admin: O&M and management operations. slow: Slow queries. query: Query operations. insert: Insert operations. update: Update operations. delete: Delete operations. command: Protocol commands, such as the aggregate method.	insert,query,update,delete
RoleType	string	No	The role of the node in the instance. Valid values: db: shard node mongos: mongos node Note Metric description This parameter applies only to sharded cluster instances. If this parameter is left empty, the default value db is used. You do not need to specify this parameter for replica set instances. Valid values: mongos : mongos node. db : shard node.	db

Response elements

Element	Type	Description	Example
	object
RequestId	string	The request ID.	E209BE2B-F264-4B9D-81F6-A5A5FB1FBF28

Examples

Success response

JSON format

{
  "RequestId": "E209BE2B-F264-4B9D-81F6-A5A5FB1FBF28"
}

Error codes

HTTP status code	Error code	Error message	Description
400	InvalidParameters.Format	Specified parameters is not valid.	The parameter entered is invalid.
400	InvalidFilterParam	Specified filter is not valid.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.