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
    • Managing dependencies
    • Request handler
    • Invocation context
    • Logging
    • Handling errors
  • Tools
  • Pricing policy
  • Access management
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ
  1. Developing in PHP
  2. Logging

PHP function runtime logging

Written by
Yandex Cloud
Updated at September 23, 2024

Cloud Functions automatically captures a PHP application's standard output streams and sends them to the centralized logging system available in Yandex Cloud. In addition to the application run history, the system logs request execution events.

Additional messages are logged using standard language constructs:

  1. print: Outputs a message to the standard output stream, stdout.
  2. print_r: Outputs information about a variable in a readable form to the standard output stream, stdout.

Note

Multiline messages must be separated by \r (carriage return) and not by \n (line feed). When using a line feed, each line is sent as a separate message and displayed separately in the log.

System messagesSystem messages

When processing each function call, the system also logs START, END, and REPORT system messages:

START RequestID: <request_ID> Version: <function_version_ID>
END RequestID: <request_ID>
REPORT RequestID: <request_ID>
    Duration: 236.606 ms
    Billed Duration: 300 ms
    Memory Size: 128 MB
    Max Memory Used: 22 MB
    Queuing Duration: 0.027 ms
    Function Init Duration: 225.298 ms

All lines contain the ID of the request (RequestID), which is generated automatically when the function is invoked.

The REPORT line provides a report on the function run. It contains additional information about the resources consumed:

  • Duration: Time spent invoking the function. It includes the Queuing Duration and Function Init Duration parameters.
  • Billed Duration: Time billed based on the pricing policy.
  • Memory Size: Amount of memory specified at version creation, MB.
  • Max Memory Used: Memory used when the request starts running.
  • Queuing Duration: Time spent by the request in the internal queue. If this time increases, it may indicate a lack of function instances. The maximum number of instances is determined by the quotas.
  • Function Init Duration: Time spent initializing the runtime and loading the function code.

Was the article helpful?

Previous
Invocation context
Next
Handling errors
© 2025 Direct Cursus Technology L.L.C.