Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Audit Trails
  • Getting started
    • Overview
    • Trail
    • Diagnostic logs
    • Comparing management and data event logs
    • Management event audit log
    • Data event audit log
    • Exporting to SIEM systems
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Management event reference
  • Data event reference
  • Release notes
  1. Concepts
  2. Diagnostic logs

Diagnostic logs

Written by
Yandex Cloud
Updated at March 7, 2025

Trail diagnostic logs contain records of changes to the status of the trail itself.
Diagnostic logs have nothing to do with events occurring to the resources the trail collects audit logs for.

The trail statuses are as follows:

  • Active: Trail is running and collecting audit logs from the available resources.
  • Error: Possible issues with the trail's destination objects or the trail itself. See our recommendations on how to recover the trail.

A running trail may enter the Error status as a result of the administrator’s mistakes, such as:

  • Changing the configuration of the destination object that Audit Trails audit logs are uploaded to (deleting a bucket in Object Storage or a Cloud Logging log group).
  • Modifying the permissions of the service account used by the configured trail, such as revoking the audit-trails.viewer, storage.uploader, or other permissions.

If the trail is recovered within three days after the Error status occurred, all audit records generated while the trail was down will be uploaded to the appropriate destination object.

If the trail is recovered more than three days after the Error status occurred, audit events uploaded to the destination object will include events generated over the 72 hours preceeding its recovery.

Was the article helpful?

Previous
Trail
Next
Comparing management and data event logs
© 2025 Direct Cursus Technology L.L.C.