# Standard output

> Standard output - View custom model runtime log events.

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-10-09T14:05:25.066094+00:00` (UTC).

## Primary page

- [Standard output](https://docs.datarobot.com/en/docs/workbench/console/activity-log/runtime-logs.html.md): Full documentation for this topic (Markdown sidecar).

## Sections on this page

- [Next steps](https://docs.datarobot.com/en/docs/workbench/console/activity-log/runtime-logs.html.md#next-steps): In-page section heading.

## Related documentation

- [NextGen UI documentation](https://docs.datarobot.com/en/docs/workbench/index.html.md): Linked from this page.
- [Console](https://docs.datarobot.com/en/docs/workbench/console/index.html.md): Linked from this page.
- [Activity log](https://docs.datarobot.com/en/docs/workbench/console/activity-log/index.html.md): Linked from this page.
- [Logs](https://docs.datarobot.com/en/docs/workbench/console/activity-log/otel-logs.html.md): Linked from this page.
- [MLOps events](https://docs.datarobot.com/en/docs/workbench/console/activity-log/mlops-events.html.md): Linked from this page.
- [Model history](https://docs.datarobot.com/en/docs/workbench/console/activity-log/model-history.html.md): Linked from this page.

## Documentation content

When you deploy a custom model, it generates log reports unique to this type of deployment, allowing you to debug custom code and troubleshoot prediction request failures from within DataRobot. These logs are accessible on the Activity logs > Standard output tab. To view the logs for a deployed custom model:

- On theDeployed workloadstab, locate the deployment, click theActions menu(oron the deploymentOverview), and then clickView logs.
- In a deployment, click theActivity logtab, and then clickStandard output.

From this tab, you can troubleshoot failed prediction requests. The logs are captured from the Docker container running the deployed custom model and contain up to 1MB of data.

> [!NOTE] No logs available
> Standard output can only be retrieved when the custom model deployment is active; if the deployment is inactive, the Standard output tab and the action menu button are disabled for inactive deployments.
> 
> In addition, even when the Standard output tab is accessible, DataRobot only provides logs from the Docker container running the custom model; therefore, it's possible for specific event logs to be unavailable when a failure occurs outside the Docker container.

You can re-request logs by clicking Refresh. Use the Search bar to find specific references within the logs. Click Download Log to save a local copy of the logs.

## Next steps

After reviewing standard output for a custom model, investigate other deployment logs and events for a fuller picture of its behavior.

- Logs : Review OpenTelemetry-standard logs from models and agentic workflows for deeper analysis and troubleshooting.
- MLOps events : Check deployment-level events, such as prediction request failures, that can help correlate with issues found in standard output.
- Model history : Review the historical log of model deployments and replacements to see if a recent change coincides with the errors in the logs.