Observability retention
Reference retention windows, capture limits, and query bounds for observability signals.
These limits describe current dashboard, CLI, and runtime capture behavior for observability signals. For platform-wide ceilings, see Limits reference.
Dashboard time windows
Typical presets:
| Surface | Windows |
|---|---|
| Observability charts | 6h, 12h, 24h, 7d |
| Logs | From about 30 minutes up to 7 days |
Metric buckets are commonly 5 minutes (≤24h windows) or 60 minutes (longer windows).
Longer archival retention is not published as a separate product SLA today.
Request list
Logs queries return a bounded number of rows per page or request (commonly up to a few hundred). Narrow the time range and filters when searching busy projects.
Function log capture
Per-invoke console capture is bounded so telemetry cannot keep the runtime open indefinitely. Approximate platform limits:
| Limit | Value |
|---|---|
| Max lines per invoke | 256 |
| Max bytes per line | 256 KiB |
| Max total captured bytes | 1 MiB |
Excess output may be dropped. Prefer concise structured logs on hot paths.
OpenTelemetry span capture
Application span buffers are bounded by count and size. Excess spans may be truncated on the Trace. See OpenTelemetry.
CLI follow
easel logs --follow polls periodically (about every 10 seconds) and respects
--timeout (default 5 minutes unless you set another value).
Delivery
Observability shipping is best-effort and must not block request handling. Do not treat Logs as a guaranteed, complete audit log for compliance without an external retention system.