Skip to main content
Use this guide when you need to answer one of two questions:
  • “What is my running app doing right now?”
  • “Why did this deploy fail or hang?”

Runtime Logs

Use floo logs for what the running app is emitting after deploy.
floo logs --app my-app
floo logs --app my-app --since 1h
floo logs --app my-app --error
floo logs --app my-app --services api
floo logs --app my-app --search "timeout"
floo logs --app my-app --live
Runtime logs are the right tool when the build succeeded but the live app is unhealthy, noisy, or returning errors.

Build Logs

Use deploy logs for what happened during build and rollout.
floo deploys list --app my-app
floo deploys logs <deploy-id> --app my-app
floo deploys logs <deploy-id> --app my-app --follow
Build logs are the right tool when a deploy never goes live or fails before traffic reaches your app.

Live Deploy Watch

Use floo deploys watch when a deploy is in flight and you want the fastest end-to-end view:
floo deploys watch --app my-app
floo deploys watch --app my-app --commit abc1234
This is the quickest way to confirm whether a push-triggered deploy is progressing, blocked, or already finished.

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. Deploy again or let the next push trigger a redeploy.
Example:
floo deploys list --app my-app
floo deploys logs <deploy-id> --app my-app
floo logs --app my-app --error --since 30m
floo env set API_KEY=... --app my-app --restart

For Agents

Use JSON mode when an agent needs to parse the result:
floo logs --app my-app --error --json 2>/dev/null | jq '.data.logs'
floo deploys list --app my-app --json 2>/dev/null | jq '.data.deploys'

Dashboard Surface

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