// MONITORING AND LOGS
Runtime Logs
Read stdout/stderr from the currently running container, right from the project's Runtime Logs page.
Every container project has a Runtime Logs page (in the project sidebar, between Deploys and Environment) showing stdout/stderr from the currently active container — the same output you'd get from docker logs on the box it's running on.
What it is
It's a point-in-time snapshot, not a live stream: open the page (or hit Refresh) and it fetches the most recent lines from the container that's active right now. Pick how many lines to pull back — 100, 200, 500, or 1000 — from the selector at the top.
How to use it
- Log meaningfully at startup and on any unhandled error — those lines are what you'll actually see here when something's wrong.
- This reads whatever container is currently active. If a bad deploy already rolled back to a previous version, you're seeing the previous version's output, not the failed one — check Build Logs for what happened during the failed deploy itself.
- It's a snapshot: a crash-looping container that restarts between refreshes can show different output each time. For anything you need a durable record of, still ship logs to your own external service.
For build-time output — dependency installs, the image build itself, health-check failures — see Read Build Logs instead; this page only covers the running container.