# Application OpenTelemetry telemetry

> Application OpenTelemetry telemetry - Where to find OTel traces, logs, and metrics your container
> emits.

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.822198+00:00` (UTC).

## Primary page

- [Application OpenTelemetry telemetry](https://docs.datarobot.com/ja/docs/workload-api/monitor-workloads/otel-telemetry.html.md): Full documentation for this topic (Markdown sidecar).

## Sections on this page

- [Where each signal surfaces](https://docs.datarobot.com/ja/docs/workload-api/monitor-workloads/otel-telemetry.html.md#where-signals-surface): In-page section heading.
- [Retention](https://docs.datarobot.com/ja/docs/workload-api/monitor-workloads/otel-telemetry.html.md#retention): In-page section heading.

## Documentation content

Application traces, logs, and metrics emitted by your container are exposed through DataRobot's OpenTelemetry (OTel) observability surface. This surface is separate from the Workload API —the API itself owns Workload-scoped request statistics, lifecycle events, and per-replica status, and does not proxy OTel data. Instead, the platform aggregates whatever your container exports through the standard OTLP endpoint and renders it in the Console.

Container stdout and stderr are captured automatically and appear on Activity log > Logs at every lifecycle stage (including startup and crash diagnostics) without any SDK setup. プラットフォームは、起動時にコンテナに対して `OTEL_EXPORTER_OTLP_ENDPOINT` （および関連する認証とリソース環境変数）を設定します（完全なリストについては、 [プラットフォームが管理する環境変数](https://docs.datarobot.com/ja/docs/workload-api/build-artifacts/artifacts-concepts.html.md#platform-managed-env-vars) を参照してください）。これにより、アプリケーションがSDKを通じてOTelシグナルを送信すると、それらは同じオブザーバビリティ基盤に到達します。 Use explicit instrumentation when you want traces, application metrics, or structured, attribute-rich logs on top of automatic capture—for copy-ready Python SDK snippets, see [Instrument a Workload with OpenTelemetry](https://docs.datarobot.com/ja/docs/workload-api/monitor-workloads/instrument-with-otel.html.md).

## Where each signal surfaces

Each OTel signal type appears on a different Console tab:

| Signal | Console tab | ページ |
| --- | --- | --- |
| Traces | Monitoring > Data exploration | Explore monitoring data |
| ログ | Activity log > Logs | View Workload logs |
| 指標 | Monitoring > OTel Metrics | View OpenTelemetry metrics |

## Retention

OTelの保持期間は、組織レベルで設定されます。 [監視の概念：保持期間の概要](https://docs.datarobot.com/ja/docs/workload-api/monitor-workloads/monitoring-concepts.html.md#retention-summary) および [OTelの保持期間の設定](https://docs.datarobot.com/ja/docs/platform/admin/otel-retention.html.md) を参照してください。