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 Cloud Functions
  • Comparison with other Yandex Cloud services
    • Overview
    • Function
    • Invoking a function
    • Asynchronous function invocation
    • Long-lived functions
    • Function termination notifications
    • Networking
    • Mounting external resources to a function file system
    • Builder
    • Dead Letter Queue
    • Function logs
    • Backups
    • Quotas and limits
  • Tools
  • Pricing policy
  • Access management
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

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

Function logs

Written by
Yandex Cloud
Updated at March 27, 2025
  • Structured logs
  • See also

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

There are two types of logs:

  • Automatic: Logs of requests to functions.
  • 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 data to the execution log. Function examples.
  • Builder. Logging.

Was the article helpful?

Previous
Dead Letter Queue
Next
Backups
© 2025 Direct Cursus Technology L.L.C.