# 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-06-22T16:50:38.252148+00:00` (UTC).

## Primary page

- [Application OpenTelemetry telemetry](https://docs.datarobot.com/en/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/en/docs/workload-api/monitor-workloads/otel-telemetry.html.md#where-signals-surface): In-page section heading.
- [Retention](https://docs.datarobot.com/en/docs/workload-api/monitor-workloads/otel-telemetry.html.md#retention): In-page section heading.

## Related documentation

- [Workload API](https://docs.datarobot.com/en/docs/workload-api/index.html.md): Linked from this page.
- [Monitor telemetry and health](https://docs.datarobot.com/en/docs/workload-api/monitor-workloads/index.html.md): Linked from this page.
- [Instrument a Workload with OpenTelemetry](https://docs.datarobot.com/en/docs/workload-api/monitor-workloads/instrument-with-otel.html.md): Linked from this page.
- [Explore monitoring data](https://docs.datarobot.com/en/docs/api/reference/sdk/data-exploration.html.md): Linked from this page.
- [View Workload logs](https://docs.datarobot.com/en/docs/workload-api/monitor-workloads/activity-logs-ui/logs.html.md): Linked from this page.
- [View OpenTelemetry metrics](https://docs.datarobot.com/en/docs/workload-api/monitor-workloads/monitoring-ui/otel-metrics.html.md): Linked from this page.
- [Monitoring concepts: Retention summary](https://docs.datarobot.com/en/docs/workload-api/monitor-workloads/monitoring-concepts.html.md#retention-summary): Linked from this page.

## 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. The platform sets `OTEL_EXPORTER_OTLP_ENDPOINT` (and any auth env vars) on your container at start time, so when your application emits OTel signals via the SDK, they reach the same observability surface. 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/en/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 | Page |
| --- | --- | --- |
| Traces | Monitoring > Data exploration | Explore monitoring data |
| Logs | Activity log > Logs | View Workload logs |
| Metrics | Monitoring > OTel Metrics | View OpenTelemetry metrics |

## Retention

OTel retention matches the Workload's artifact lifecycle status: 24 hours for `draft` artifacts and 30 days for `locked` artifacts. After retention elapses, OTel data is automatically deleted. See [Monitoring concepts: Retention summary](https://docs.datarobot.com/en/docs/workload-api/monitor-workloads/monitoring-concepts.html.md#retention-summary) for the full retention model.