Logs
Shiprr exposes logs from the build and runtime layers so you can diagnose dependency failures, startup problems, health check failures, and crashes.
Build logs#
Build logs contain install, compile, and image build output for a specific build. Use them when dependency installation, framework compilation, asset generation, or image creation fails.
Deployment logs#
Deployment logs help connect a build result to a rollout attempt. Use them with deployment status when a build succeeds but the app fails during startup, health checks, or placement.
Runtime logs#
Runtime logs are a one-shot tail of stdout/stderr from the current running replica under App → Logs. Use them for crashes, bad configuration, missing environment variables, and startup failures after deploy.
What to check first#
- Build failed — Open the build log and review the last failing step.
- Deploy failed after build — Review deployment status, health checks, and runtime logs.
- App is live but unhealthy — Check health check path, start command, env vars, and resource limits.
Retention#
Build logs are read from archived storage when available, with platform runtime logs as a fallback. Runtime logs come from the current running replica and are not long-term log storage. Export important diagnostics or forward logs to your own system if you need longer retention.