Appearance
Deployment & Runtime Logs
Deployment (build) logs
Every deployment has its own log, streamed live from the moment it starts: cloning your repo, installing dependencies, running your build command, and deploying the result. Each line is tagged with the phase it happened in (CLONING, INSTALLING, BUILDING, ...), so when a build fails you can tell at a glance whether it failed installing dependencies or running your actual build command — the failure message says which, and the log itself shows exactly where the tag switches over.
Past deployments keep their logs too — useful for comparing what changed between a working deploy and a broken one.
Runtime logs (Web Service and Cron Job)
Once a Web Service is running, its live stdout/stderr is available as a runtime log stream — whatever your app prints is what shows up here, in real time. A Cron Job's runtime log is scoped per execution, so you're looking at exactly one run's output rather than everything the service has ever printed.
Health-check and monitoring traffic is filtered out automatically. Infrly's own platform-level checks (confirming your service is still up, watching its uptime) hit your app continuously by design — without filtering, that would drown out real traffic in the log and make it look far noisier than it actually is. What you see in the runtime log is your actual traffic, the same as if you were running the app locally and watching its own console output.
A Static Site has no runtime logs
There's no running process after a Static Site's build finishes, so there's nothing to stream — its build log is the only log it ever has. See Deploy a Static Site.