# View Workload logs

> View Workload logs - Use the Logs tab to view, filter, search, and copy container logs
> (stdout/stderr and optional OTel log records) for the Workload.

This Markdown file sits beside the HTML page at the same path (with a `.md` suffix). It summarizes the topic and lists links for tools and LLM context.

Companion generated at `2026-07-30T11:40:01.819204+00:00` (UTC).

## Primary page

- [View Workload logs](https://docs.datarobot.com/ja/docs/workload-api/monitor-workloads/activity-logs-ui/logs.html.md): Full documentation for this topic (Markdown sidecar).

## Documentation content

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](https://docs.datarobot.com/ja/docs/api/reference/sdk/data-exploration.html.md) tab.

> [!TIP] Explicit OTel instrumentation is optional
> Automatic `stdout` / `stderr` capture means you don't need the OTel SDK to view stdout/stderr logs in this tab. Add explicit instrumentation only when you want structured, attribute-rich log records alongside automatic capture—see [Instrument a Workload with OpenTelemetry](https://docs.datarobot.com/ja/docs/workload-api/operate-workloads/endpoints-ui/instrumentation.html.md).

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](https://docs.datarobot.com/ja/docs/workload-api/operate-workloads/endpoints-ui/instrumentation.html.md).

> [!NOTE] Retention
> Log retention depends on the artifact lifecycle status: 24 hours for Workloads backed by `draft` artifacts and 30 days for Workloads backed by `locked` artifacts. After retention elapses, log data is automatically deleted.

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`.

| コントロール | 説明 |
| --- | --- |
| 範囲（UTC） | ログの日付範囲（直近15分、直近1時間、直近1日、またはカスタム範囲）を選択します。 |
| レベル | 表示するログレベル（デバッグ、情報、警告、エラー、または重要）を選択します。 |
| アーティファクト | Filter logs by artifact version. Select a specific artifact to narrow log output to that deployment. |
| レプリカ | Filter logs by replica. Select a specific replica to isolate output from a single pod instance. |
| 表示を更新 | Refresh the contents of the Logs tab to load new logs. |
| ログをコピー | Copy the contents of the current Logs tab view. |
| 検索 | 指定されたテキストを含むログ行を抽出します。 複数の用語を追加すると、それらすべてが含まれている行のみが表示されます。 |
| 除外する | 指定されたテキストを含むログ行を除外します。 複数の用語を追加すると、いずれかに一致する行はすべて除外されます。 |

For the Workload API monitoring surfaces (statistics, events, history), see [REST: Monitor Workloads](https://docs.datarobot.com/ja/docs/workload-api/monitor-workloads/monitoring-rest-endpoints.html.md).