Overview
The Cloud Hooks log records all messages sent to the standard output stream (STDOUT) during Cloud Platform Hook execution. However, this log does not capture messages if you redirect your logs to a log file on the filesystem or if your custom code does not produce any logs. This log is specific to Cloud Next environments.
Parsing the log file
The following line is a representative example of the data written into your Cloud Hooks log:
2025-05-19T05:35:42.591265047Z command-5578dd9cd7-dxhwd: <log_message>| Position | Data | Description |
|---|---|---|
| 0 | 2025-05-19T05:35:42.591265047Z | The date and time the request was received by the backend infrastructure in the rfc3339 format. This field has nanosecond precision. |
| 1 | command-43a2da6e-94c7-48dc-be21-4556fdbef3b3-29129055-vl4wf | The pod name. You can use the following regex to retrieve the UUID: Use the UUID to precisely trace each log back to its originating cron job. |
| 2 | log_message | The log message. |