View Workload logs¶

A Workload's Logs tab receives container output in real time. Container stdout and stderr are captured automatically at every lifecycle stage—startup, running, and errored—including plain print() output, subprocess output, and logs from containers that haven't been instrumented with the OpenTelemetry (OTel) SDK. Startup failures and crash-loop diagnostics flow into the same log stream as runtime output, so you can inspect crash causes alongside healthy-state output in one place. Logs persist after a Workload is stopped or deleted, and are segmented per replica and per container. Additionally, you can filter and view span-specific logs on the Monitoring > OTel tracing tab.

The collected logs provide time-period filtering capabilities, and the OTel logs API is available to programmatically export logs with similar filtering capabilities. OTel-instrumented logs are standardized for export to third-party observability tools like Datadog. Plain stdout capture appears in this tab but is not OTLP-exported unless you add the logging handler described in Instrument a Workload with OpenTelemetry.

To access the logs for a Workload, on the Deployed Workloads tab, locate and click the Workload, click the Activity log tab, and then click Logs. The logging levels available are INFO, DEBUG, WARN, CRITICAL, and ERROR.

For the Workload API monitoring surfaces (statistics, events, history), see REST: Monitor Workloads.