Logs

Shiplon keeps two kinds of logs: what happened during a deployment, and what your running app prints.

Deployment logs

Open any deployment from the app’s Deployments list. Its page shows each stage as it happens:

• Fetch: which commit was fetched.
• Build: the full output of your install and build commands, or of docker build.
• Deploy: starting the new version, the health check, and switching traffic.

The log updates live while the deployment runs, and stays available afterwards.

If the new version crashes on start, the deploy log includes the last lines your app printed before it exited, so you can usually see the error without anything else.

Runtime logs

Everything your app writes to standard output or standard error (console.log, print, framework request logs) appears under Runtime logs on the app page.

• Click Show live logs to follow the output as it happens. It starts with recent lines, and keeps following through a new deployment.
• Click Pause to stop the view while you read, and Resume to carry on.
• The view keeps the most recent 2,000 lines.

If the stream is interrupted, it reconnects by itself; if it can’t, click Resume.

Tip

Log to standard output rather than to files. Files written inside the app are lost when it restarts or redeploys, and they don’t appear here.

Good logging practice

• Write one line per event, with enough context to search later: the request path, status code, and an ID.
• Never log secrets: passwords, tokens, full card numbers or the values of your environment variables.
• Log errors with their stack trace, which is what you’ll need when a deployment fails its health check or the app crashes.