Request analytics

Request analytics summarizes traffic handled by an Easel project.

Use it to understand:

• Request volume
• Response status and error rate
• Latency and compute
• Cache effectiveness
• Function starts (cold vs warm)
• Bandwidth
• Deployment-scoped activity

Where to look

1. Open the project.
2. Open Observability for charts over a time window.
3. Open Logs for the request list behind a spike.
4. Select a request to open detail, log lines, and Trace.

Typical Observability charts include:

• Edge Requests: request volume and error rates at the edge
• Edge Bandwidth: bytes served (incoming and outgoing)
• Function Starts: cold versus warm starts
• Functions and Compute: invocations, errors, and duration

Pick a deploy window and compare it to the hours before the release. When a chart moves, use Logs or Invocations to inspect the requests behind the spike.

Filters

In Logs, useful filters include:

• Time range (for example 30 minutes to 7 days)
• Environment (production or preview)
• Method
• Status
• Path and route
• Host
• Cache status
• Console level
• Deployment ID

Use invocationId:… style filters when jumping from an Invocation to its requests.

From charts to requests

A practical workflow:

1. Confirm the time window and environment on Observability.
2. Note which chart moved (errors, bandwidth, cold starts, compute).
3. Open Logs for the same window.
4. Filter to the failing status, path, or deployment.
5. Open a request for detail and Trace.

Related guides

• Request details
• Metrics
• Logs
• Function observability