Skip to main content
You can filter audit events when viewing or exporting them to narrow down the results. The filter syntax is the same for both operations, with one exception: the authentication.subject.name filter is not available in exports because it can contain email addresses that are personally identifiable information (PII).

Prerequisites

  1. Make sure you are in a group that has the admin or auditlogs.audit-event-viewer role within your tenant to view events. To export events, use a group that has the admin or auditlogs.audit-event-exporter role and make sure that you have the storage.uploader role for the destination bucket. You can check group membership in the Administration → IAM section of the web console.
  2. Identify the regions to search for the audit events you need and the regions to export audit events from.

Filter operators

Supported operators include:
  • = equals
  • != not equals
  • : contains
  • regex regular expression match

How to filter events in the web console

To narrow down the events, you can use the following filters:
  • Event JSONs: Search in JSON field values, but not a full-text search for a substring in the JSON event description. For example, if the JSON contains a name field with the value Test User, this filter finds Test User but cannot find "name": "Test User".
  • Action: Standard actions are CREATE, UPDATE or DELETE. Actions can differ by service. For example, for Compute resources, you can also specify STOP and START.
  • Ancestor ID: ID of the resource ancestor, starting from the tenant.
  • Ancestor name: Name of the resource ancestor, starting from the tenant.
  • Masked token: Access token that was used to authorize the event. You can enter a part of the token here.
  • Resource ID: ID of the resource on which actions were performed. For example, a Compute disk (computedisk-***), a service account (serviceaccount-***), etc.
  • Resource name: Name of the resource on which actions were performed.
  • Resource type: Type of the resource on which actions were performed. For example, computedisk or mk8scluster.
  • Service: Service in which the actions were performed.
  • Event class: String in the ai.nebius.<service_name>.<resource_type>.<action> format. It includes the ai.nebius prefix and refers to a Nebius AI Cloud service, type of resource in it, and the action performed on this resource, for example, ai.nebius.compute.computeinstance.delete.
  • Static key ID: ID of the static key that was used to authorize the event.
  • Status: Status of the operation associated with the event.
  • Subject ID: ID of a user account or a service account that performed actions. The formats of user account IDs and service account IDs are tenantuseraccount-*** and serviceaccount-***.
  • Subject name: Name of a user account or a service account that performed actions. This filter is not available for exports.
Click = in a filter to choose if the events should contain or exclude the values you enter.

How to filter events by using the CLI or an SDK

To narrow down the events, you can use one or more of the following filters. For the other parameters of a list request, see Viewing events in Audit Logs. For the other parameters of an export, see How to export audit events to Object Storage.
  • Resource ID or type The type or ID of the resource on which actions were performed. ID formats include, for example, a computeinstance-*** for a Compute virtual machine, computedisk-*** for a Compute disk, serviceaccount-*** for a service account.
    List events by resource type:
    List events for a resource ID:
    Start an export by resource type:
    Start an export for a resource ID:
  • Resource ancestor ID or name The ID or name of the resource ancestor, starting from the tenant. For example, you can check all the actions performed on virtual machines in one of your projects by specifying the project ID or name.
    List events by ancestor ID:
    List events by ancestor name:
    Start an export by ancestor ID:
    Start an export by ancestor name:
  • Event action Specify the action: CREATE, UPDATE or DELETE. Actions can differ by service. For example, for Compute resources, you can also specify STOP and START.
    List events by action:
    Start an export by action:
  • Service in which the event occurred. See the list of services.
    List events by service:
    Start an export by service:
  • Event class A string in the ai.nebius.<service_name>.<resource_type>.<action> format. It includes the ai.nebius prefix and refers to a Nebius AI Cloud service, type of resource in it, and the action performed on this resource, for example, ai.nebius.compute.computeinstance.delete.
    List events by event class:
    Start an export by event class:
  • Subject name or ID The name or ID of a user account or a service account that performed actions. The formats of user account IDs and service account IDs are tenantuseraccount-*** and serviceaccount-***. The authentication.subject.name filter is not available for exports.
    List events by subject name:
    List events by user account ID:
    List events by service account ID:
    Start an export by user account ID:
    Start an export by service account ID:
  • Subject credentials For access tokens, use authentication.token_credential.masked_token without a signature. For AWS-compatible access keys, use authentication.static_key_credential.id.
    List events by masked token:
    List events by static key ID:
    Start an export by masked token:
    Start an export by static key ID:

How to combine filters

To combine filters, use the following options:
  • AND logical operator.
  • Comparison operators: = (equals), != (not equals), : (contains).
  • Regular expressions (for example, regex(resource.name, '^.*prod.*$') to show resources with prod in their names).

Examples

For example, to view events where the user example@nebius.com deleted virtual machines:
In the command, specify:
  • --parent-id: Tenant ID.
  • --start: Start time for the search, in the ISO 8601 format.
  • --end: End time for the search, in the ISO 8601 format.
  • --filter: authentication.subject.name for example@nebius.com, action='DELETE', and resource.metadata.type='computeinstance'.
  • --region: Region where the events are stored.
For example, to export events where a specific user deleted virtual machines between April 1 and April 5:
In the command, specify:
  • --parent-id: Tenant ID.
  • --params-from: 2025-04-01T00:00:00Z.
  • --params-to: 2025-04-06T00:00:00Z.
  • --params-event-type: control_plane or data_plane.
  • --nebius-object-storage-bucket-by-id-id: Destination bucket ID (metadata.id). See How to export audit events to Object Storage.
  • --nebius-object-storage-object-prefix (optional): Object prefix. If you omit it, the auditlogs prefix is used.
  • --params-filter: authentication.subject.tenant_user_id, action='DELETE', and resource.metadata.type='computeinstance'.
  • --region: Region where the events are stored.
For more details about the fields, see Structure and fields of events in Audit Logs.