Skip to main content
floo analytics shows what changed after a deploy. Alert rules notify you before users do.

​
Analytics from the CLI

Use floo analytics to inspect traffic, error rate, latency, and status-code mix for an app or an org.
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

An alert rule watches one metric over a rolling window and notifies you when it crosses a threshold. Create and manage rules per app on the dashboard, under App → Alerts → Alert rules. For example, “error rate gt 0.05 over 15 minutes, email the on-call address” catches a bad deploy before a user reports it. Alert rules live in the operational surface rather than in floo.app.toml because they describe live behavior and carry notification targets, not app shape. There is no CLI command for them; the same Alerts tab also holds error routing, which routes failed deploys and repeating errors to an agent.
  1. Watch deploys and logs during rollout.
  2. Use analytics to see what changed over the following hours or days.
  3. Add alert rules on App → Alerts for the thresholds you care about.
  4. Pair them with agent webhooks when you want enriched incident routing as well as simple notification.

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.