Monitoring

Every Halo deployment ships with telemetry on by default. You see traffic at the edge, errors per route, and structured logs from your runtime — all in the dashboard or via the CLI.

Live logs

halo logs --tail

Streams over a long-poll WebSocket. Filter:

halo logs --tail --route /api/checkout --status '>=500'

Metrics

The dashboard exposes:

• p50 / p95 / p99 latency — per route, per region.
• Requests per second — broken down by status class.
• Error rate — 4xx and 5xx as separate series.
• Cold start rate — for edge functions, the share of invocations hitting a fresh isolate.

All metrics are pulled at 10s resolution and retained for 30 days.

Alerts

halo alerts add \
  --name "checkout 5xx" \
  --route /api/checkout \
  --metric error_rate \
  --threshold 0.02 \
  --window 5m \
  --notify slack:#oncall

Notify channels: slack, email, webhook, pagerduty.

Exporting to your stack