Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Audit Trails
  • Getting started
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Management event reference
  • Data event reference
    • Overview
  • Release notes
  1. Audit log reference
  2. Overview

Audit log reference

Written by
Yandex Cloud
Updated at October 16, 2026
View in Markdown

This reference contains the JSON structure and field descriptions for events collected by Audit Trails. Use it to analyze audit logs, build search queries, and configure filtering. Management and data events are provided together.

Each event page has two sections:

  • Event JSON schema: Event record structure, including nested objects and arrays.
  • Field description: Description of fields, their types, and possible values.

This reference lists the possible fields for each event. The fields available in an actual log depend on the event and resource parameters.

Field names in the reference and logsField names in the reference and logs

The reference uses camelCase for compound field names, while audit logs generally use snake_case, with lowercase letters and _ as separators. When matching paths, pay attention to the naming convention and casing of each nested field.

Here is an example for a BucketUpdate event:

In the reference

In the log

eventType

event_type

requestMetadata.remoteAddress

request_metadata.remote_address

details.bucketId

details.bucket_id

details.maxSize

details.max_size

details.settingsReadAccess

details.settings_read_access

Single-word names, such as details, remain unchanged. This rule applies to field names, not field values: the event type remains yandex.cloud.audit.storage.BucketUpdate.

Nested data may retain the format used by the source service. When building queries and configuring filters, use the exact key names and casing from the actual JSON log.

Was the article helpful?

Previous
Data event reference
Next
ComputeNodeAccess
© 2026 Direct Cursus Technology L.L.C.