Runtime logs

Every service has a Logs tab showing its live output — no setup, no external tooling required. Helicarrier collects your container’s stdout and stderr and keeps a rolling window you can browse and search.

Live streaming

Open the Logs tab and you see recent output first, then new lines stream in live as your service runs. The view auto-scrolls as logs arrive. Because logs are captured server-side, they:

• Survive redeploys — unlike raw docker logs, your history is not wiped when a new container replaces the old one.
• Persist for stopped services — a service that has stopped still shows its last output.

Search

Use the search box to filter by substring — including partial and digit matches — powered by a per-line index, so search stays fast even over a lot of output. Scroll up to load older lines; matches paginate the same way.

Color and formatting

The viewer renders your app’s own ANSI color codes (from loggers like winston, pino, or chalk). Plain lines are tinted by detected level — errors in red, warnings in amber, debug dimmed — each with its timestamp, so problems stand out at a glance.

7-day retention

Runtime logs are retained for 7 days. The Logs tab shows a 7-day retention badge to make the window explicit; older lines are automatically deleted. If you need logs for longer — for compliance or long-term analysis — forward them to an external service with a log drain.

Build logs vs runtime logs

These are distinct:

• Runtime logs (this page) are your running container’s output.
• Build logs are the output of each deployment’s build, shown per-deployment in the Deployments tab.

Next

Keep logs longer or centralize them with Log drains.