Skip to main content
Talk to us
Observe

Observability troubleshooting

Diagnose missing logs, incomplete traces, and request-correlation problems.

Start with a request ID, deployment ID, invocation ID, or exact timestamp whenever possible.

A request does not appear

Check:

  • Selected time range
  • Project and environment filters
  • Deployment ID
  • Domain or host filter
  • Whether the request hit a different project
  • Brief ingest delay after the request completed

Very early platform-only traffic without project attribution may not appear in project Logs.

Logs are missing

Check:

  • The function actually ran (cache HIT and static responses produce little or no function output)
  • The selected deployment and environment
  • Console level filters
  • Whether capture limits dropped excess lines
  • Whether the process exited before flush on a crash path

Traces look empty under Invoke function

Platform spans still appear without application instrumentation. To see nested app spans:

  1. Confirm OpenTelemetry registration in the runtime.
  2. Deploy the instrumented build.
  3. Hit a path that exercises the instrumented code.
  4. Re-open Logs → Trace.

See OpenTelemetry.

AWS billed or init fields are empty

AWS duration, billed duration, and init come from the function wake telemetry report. They attach to the invocation and can arrive slightly after the HTTP response completes. Open Invocations for the wake, or refresh request detail after a short delay.

Cache status disagrees with expectations

  1. Read X-Easel-Cache on the live response.
  2. Confirm Cache-Control and cookies on the origin response.
  3. See Cache observability and CDN troubleshooting.

Firewall badge is Allow but the client saw a challenge

Challenge and platform decisions can short-circuit before ordinary application handling. Confirm Attack Mode and custom rules in project settings, and see Security events.

Metrics and Logs disagree slightly

Charts aggregate over buckets; Logs lists individual requests. Align the time window, environment, and deployment filters. Expect brief ingest delay and best-effort delivery.

Information to include with support

Include:

  • Workspace and project
  • Deployment ID
  • Request ID
  • Invocation ID when relevant
  • Approximate timestamp and timezone
  • Environment and domain
  • Expected versus observed behavior
  • Screenshot or CLI output of easel logs --request-id … --expand

Related guides

Retention

Reference retention windows, capture limits, and query bounds for observability signals.

Performance guide

Improve application latency, cache efficiency, build speed, and Function resource usage on Easel.

On this page

A request does not appearLogs are missingTraces look empty under Invoke functionAWS billed or init fields are emptyCache status disagrees with expectationsFirewall badge is Allow but the client saw a challengeMetrics and Logs disagree slightlyInformation to include with supportRelated guides
Edit on GitHub