Skip to main content
Once an app is live, you need two things:
  • a way to see what changed after a deploy
  • a way to get notified before users tell you something is broken
Floo’s production surface covers both.

​
Analytics from the CLI

Use floo analytics to inspect traffic, error rate, latency, and status-code mix for an app or an org. 
floo analytics my-app
floo analytics my-app --period 7d
floo analytics my-app --json 2>/dev/null | jq '.data'
This is the fastest way to answer questions like:
  • did requests drop after the last deploy?
  • is error rate trending up?
  • did latency regress?

​
Alert rules in the app surface

The shipped platform surface also supports app-level alert rules. Use them when you want thresholds to notify humans or downstream workflows before a runtime issue turns into guesswork. Alert rules belong in the live operational surface because they are about monitoring live behavior, not describing app shape in git.
  1. Watch deploys and logs during rollout.
  2. Use analytics to see what changed over the following hours or days.
  3. Configure alert rules for thresholds you care about.
  4. Pair alerts with agent webhooks when you want incident routing as well as simple notification.
floo analytics my-app
floo logs --app my-app --error
floo deploys list --app my-app

Logs and Debugging

Use logs and deploy history to understand the incident in detail.

Agent Webhooks

Route richer incident context to your agent or on-call workflow.