App logs and versioning

Domino provides detailed logging and version tracking for apps to support debugging, improve reliability, and provide operational transparency. This guide outlines the available logs and metadata, how to access and interpret them, and how Domino handles versioning for published apps.

App logs

Domino captures a range of logs during app execution to help you monitor performance, troubleshoot issues, and understand system behavior. These logs offer visibility into both your app code and the underlying platform infrastructure.

Available logs

When viewing or troubleshooting an app, the following types of logs may be available:

  • App stdout/stderr: Captures standard output, error messages, and runtime print statements.

  • Kubernetes events: Includes pod scheduling, image pulls, and container state transitions.

  • Execution logs: Generated by Domino’s execution engine for each app run.

  • System logs: Captures platform-level components such as executor, logjam, and frontend services.

  • NGINX & nucleus logs: Provide visibility into routing, proxy behavior, and request handling.

  • Performance metrics (optional): CSV-format data that tracks system-level performance like CPU and memory.

Accessing logs

You can access logs directly from the App UI or download them for deeper inspection. Domino also provides a Support Bundle that consolidates key logs and metadata for comprehensive troubleshooting.

Support bundle contents

The support bundle is a downloadable archive that includes comprehensive logs and metadata:

  • execution.log, executor.log – App subprocess execution and engine output.

  • events.json, events.csv – Timeline of internal execution events.

  • kubernetes-events.json – Cluster and pod lifecycle messages.

  • logjam-*.log – Runtime traces and orchestration activity.

  • nginx.log, nucleus-*.log – Proxy and routing behavior.

  • execution.yaml, manifest.csv – Runtime configuration and file manifest.

  • performance-metrics.csv (optional) – System resource utilization metrics.

  • project.json – Project-level settings and environment metadata.

  • run.json – Detailed run metadata, diagnostics, and resource info.

  • run-history.json – Sequence of lifecycle status changes.

  • saga.json – Infrastructure orchestration details and container startup data.

These files provide full insight into runtime behavior, app infrastructure, and system performance.

App version control

Domino automatically tracks versions of your app each time it’s published. This version history helps you audit changes, review configuration details, and trace issues across deployments.

Automatic versioning

Every time you publish an app, Domino captures a version snapshot. Each version includes metadata such as:

  • Linked environment

  • File references

  • Code paths

Usage

Domino Apps maintain a version history that you can view directly from the App UI. This lets you browse and inspect previous versions for auditing, debugging, or review purposes—especially helpful when tracking changes over time or reviewing how a particular configuration behaved in the past.

Note

While version history is available for reference, Domino does not currently support rollback or diff comparisons between versions.

Best practices

To ensure your Apps run reliably and are easy to maintain, follow these best practices during development, deployment, and monitoring. These tips can help you catch issues early, maintain reproducibility, and support smooth collaboration across teams.

  • Use support bundles to investigate failed or abnormal app behavior.

  • Validate environments before publishing to ensure consistency and reproducibility.

  • Audit version metadata to track deployments and operational history.

  • Review logs regularly, especially after environment updates or dependency changes.

Troubleshooting tips

If your App isn’t behaving as expected, these quick diagnostics can help you identify and resolve common issues:

  • No output in logs? Check executor.log and logjam-*.log for errors.

  • Scheduling issues? Inspect kubernetes-events.json for pod failures or capacity problems.

  • Unexpected behavior after publishing? Compare version metadata and environment differences.

Next steps

  • Apps in Domino gives an overview of how apps work within the Domino ecosystem.

  • Create and Publish an App has instructions on creating and publishing your Apps, customizing the App’s URL, and sharing Apps with authorized users.

  • Learn more about how Apps in Domino run and what identity and permissions are used.