Request details
Inspect the complete path of a single request through Easel.
The request detail view connects one client request to the deployment, route, cache decision, function work, and logs that handled it.
Request identity
Each request has a stable request ID. Easel also returns it to clients as
X-Easel-Id.
Use the request ID to:
- Search Logs and the CLI (
easel logs --request-id …) - Correlate function log lines and Trace spans
- Contact support
- Jump between related views
The request ID is a UUID string generated at the edge.
Open a request
- Open the project and go to Logs.
- Filter to the time range and path you care about.
- Select a request row.
- Review the detail panel.
- Use the dock tabs Logs and Trace.
From detail you can also open the matching invocation when one exists.
Summary fields
A request summary commonly includes:
- Request ID
- Timestamp (request started)
- Host
- Method and path
- Status code
- User agent and referer when available
- Firewall badge when a security action is present
- Function and middleware indicators when compute ran
Timing and function fields
When a function handled the request, the detail panel can show:
| Field | Meaning |
|---|---|
| Compute duration | Time executing customer function code through response body completion |
| Post-response | Work after the response finishes (for example waitUntil / flush) |
| AWS duration | Lambda-reported duration for the wake |
| AWS billed | Lambda-reported billed duration for the wake |
| AWS init | Initialization time when the wake was a cold start |
| Cold start | Whether this invoke initialized a new runtime process |
| Invocation ID | AWS request ID for the function wake |
| Instance | Lambda instance identity for the wake |
AWS duration, billed duration, and init apply to the invocation (the wake), not always as independent per-HTTP-request meters. Use Invocations when one wake served multiple requests.
These fields sit on the detail panel. They are not separate Trace span names.
Dock: Logs and Trace
The sticky dock under the list has two tabs for the selected request:
- Logs: function and platform log lines for that request
- Trace: the span tree for edge and function work on that request
What detail does not replace
- Cold start and AWS billed context also appear on Invocations.
- Build failures appear in deployment build logs, not request detail.
- Cache policy diagnosis often needs the
X-Easel-Cacheresponse header in addition to Logs filters. See Cache observability.