floo analytics shows what changed after a deploy. Alert rules notify you before
users do.
Analytics from the CLI
floo analytics reports traffic, error rate, latency, and status-code mix for an app, or for the org when you omit the app.
- 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, or through the API at/v1/apps/{app_id}/alerts.
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 are not in floo.app.toml: they describe live behavior and carry
notification targets, not app shape. There is no CLI command for them. The same
Alerts tab holds
error routing, which routes failed deploys
and repeating errors to an agent.
Recommended operating loop
- Watch deploys and logs during rollout.
- Use analytics to see what changed over the following hours or days.
- Add alert rules on App → Alerts for the thresholds you care about.
- Pair them with agent webhooks to route enriched incident context, not only a notification.
Related commands
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.