App logs
These log types are available during and after App execution:- 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.
Logs per version and per instance
Domino organizes logs by version. Because a version can be started many times, an instance selector on the App details page lets you read the logs from one specific run. A new version starts its logs fresh. Resource consumption (CPU and memory) is recorded per instance. Use the instance selector to view metrics from each start of the version.Accessing logs
Read logs directly from the App UI or download them for deeper inspection. Domino also produces a support bundle that consolidates key logs and metadata for troubleshooting.Support bundle contents
The support bundle is a downloadable archive:-
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.
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.logandlogjam-*.logfor errors. -
Scheduling issues? Inspect
kubernetes-events.jsonfor pod failures or capacity problems. - Unexpected behavior after a deploy? Compare the running version’s configuration against the version that last worked, then start the older version to confirm.
Best practices
- Use support bundles to investigate failed or abnormal app behavior.
- Review logs regularly, especially after environment updates or dependency changes.
- Compare a failing version against the last good one by reading each version’s configuration, then start the older version to confirm the difference.
Next steps
- App versioning and reproducibility: What a version pins, and how to start a previous one
- Apps in Domino gives an overview of how apps work within the Domino ecosystem.
- Publish and deploy App versions: Create an immutable version, then start it for viewers
- Learn more about how Apps in Domino run and what identity and permissions are used.