# Model logs for model packages (legacy)

> Model logs for model packages (legacy) - View the model logs for a model package to see a history of
> the successful operations (INFO status) and errors (ERROR status).

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-04-24T16:03:56.570193+00:00` (UTC).

## Primary page

- [Model logs for model packages (legacy)](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/registry/reg-model-pkg-logs.html): Full documentation for this topic (HTML).

## Related documentation

- [Classic UI documentation](https://docs.datarobot.com/en/docs/classic-ui/index.html): Linked from this page.
- [MLOps](https://docs.datarobot.com/en/docs/classic-ui/mlops/index.html): Linked from this page.
- [Deployment](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/index.html): Linked from this page.
- [Register models](https://docs.datarobot.com/en/docs/classic-ui/mlops/deployment/registry/index.html): Linked from this page.

## Documentation content

# Model logs for model packages (legacy)

> [!NOTE] Availability information
> Model logs for model packages in the Model Registry are off by default, requiring the deprecated legacy Model Packages tab. Contact your DataRobot representative or administrator for information on enabling this feature.
> 
> Feature flags: Enable Legacy Model Registry

On the deprecated legacy Model Packages tab in the Model Registry, the Model Logs tab displays information about the operations of the underlying model. This information can help you identify and fix errors. For example, compliance documentation requires DataRobot to execute many jobs, some of which run sequentially and some in parallel. These jobs may fail, and reading the logs can help you identify the cause of the failure (e.g., the Feature Effects job fails because a model does not handle null values).

> [!NOTE] Model logs consideration
> In the Model Registry, a model package's Model Logs tab only reports the operations of the underlying model, not the model package operations (e.g., model package deployment time).

To view the model logs for a model package:

1. In theModel Registry, click theModel Packagestab.
2. Click a model package in the list, and then clickModel Logs.
3. On theModel Logstab, review the timestamped log entries: InformationDescription1Date / TimeThe date and time the model log event was recorded.2StatusThe status the log entry reports:INFO: Reports a successful operation.ERROR: Reports an unsuccessful operation.3MessageThe description of the successful operation (INFO), or the reason for the failed operation (ERROR). This information can help you troubleshoot the root cause of the error.
4. If you can't locate the log entry for the error you need to fix, it may be an older log entry not shown in the current view. ClickLoad older logsto expand theModel Logsview. View older logsLook for the older log entries at the top of theModel Logs; they are added to the top of the existing log history.