Skip to main content
Runtime logs show what a live app is doing. Build logs show why a deploy failed. Start with floo doctor. floo doctor accounts --app my-app and floo doctor managed-services --app my-app each return one verdict with its evidence in one round trip, so you do not correlate the gateway, request logs, and config by hand.

​
Runtime logs

Use floo logs query for a bounded result and floo logs tail for a continuous stream.
Use runtime logs when the build succeeded but the live app is unhealthy, noisy, or returning errors. For gateway request history filtered by app key, use GET /v1/apps/{app_id}/requests?api_key_id={key_id} with an operator credential. See App API keys and request history for time filters, pagination, and retention limits.

​
Build logs

Deploy logs cover build and rollout.
Use build logs when a deploy never goes live or fails before traffic reaches your app.

​
Live deploy watch

floo deploys watch follows an in-flight deploy end to end:
It shows whether a push-triggered deploy is progressing, blocked, or finished. For scripts and agents, floo deploys status --app my-app --json returns the same answer as phase booleans without streaming build logs. host_bound is true only when the deploy is live, the gateway URL is wired, and the app is live. host_bound: false with a live deploy means the service may serve on its internal URL while users cannot reach it through the gateway.

​
A practical debug loop

  1. Find the deploy you care about.
  2. Read build logs if the deploy failed before going live.
  3. Read runtime logs if the deploy succeeded but the app is broken.
  4. Fix config or env vars.
  5. Redeploy, or let the next push deploy.
Example:

​
For agents

An agent reads the same data through the CLI with --json, or through the HTTP API at GET /v1/apps/{app_id}/logs and GET /v1/apps/{app_id}/deploys:

​
Dashboard surface

The shipped app detail view exposes:
  • service logs panels
  • deploy history panels
  • service-level status and env views
The CLI is better for scripted filters, streaming, and copy-paste debugging loops.

Agent webhooks

Route failed deploys and repeating runtime errors to your agent or on-call workflow.

Releases and rollbacks

Recover quickly when the right move is shifting traffic back.