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
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Yandex Serverless Containers
  • Comparison with other Yandex Cloud services
    • Overview
    • Container
    • Invoking a container
    • Runtime environment
    • Networking
    • Mounting external resources to a container file system
    • Long-lived containers
    • Container termination notifications
    • Dead Letter Queue
    • Container logs
    • Backups
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

  • Structured logs
  • See also
  1. Concepts
  2. Container logs

Container logs

Written by
Yandex Cloud
Updated at April 9, 2024
  • Structured logs
  • See also

A container writes logs to Yandex Cloud Logging, to the default log group for the folder where the container is located.

There are two types of logs:

  • Automatic: Logs of requests to containers.
  • Custom: Logs that custom code writes to the standard output (stdout) and standard error output (stderr). The minimum logging level of custom logs is UNSPECIFIED.

Learn more about working with logs in the Yandex Cloud Logging documentation.

Structured logsStructured logs

Apart from text, structured logs in the following JSON format can be written to the stdout and stderr standard output streams:

  • message/msg: Entry text.
  • level: Logging level. Possible logging levels: TRACE, DEBUG, INFO, WARN, ERROR, and FATAL.
  • stream_name: Log stream name. Length: 1 to 63 characters.

All other JSON fields are automatically written to json-payload.

A log must be single-line. Any entry that contains the message/msg field and is up to 64 KB is considered to be a structured log. If the entry size is larger, it is split into multiple records and treated as text.

You can disable structured logs by setting the STRUCTURED_LOGGING = false environment variable. In this case, any JSON log will be considered plain text.

See alsoSee also

  • Writing information to the execution log. Application and Dockerfile examples.

Was the article helpful?

Previous
Dead Letter Queue
Next
Backups
Yandex project
© 2025 Yandex.Cloud LLC