Observe

Observability

See how Easel handled each request, from security and cache to function work, and how traffic changed after a deploy.

Easel observability connects each request to the deployment, route, cache result, function work, and security decision that handled it. Every request gets a request ID, so you can move from a chart to the request behind it and then to its Trace.

Surfaces

Open a project and use these views:

View	Use it for
Observability	Charts of traffic, bandwidth, function starts, and compute, plus custom queries
Logs	Individual requests, their log lines, and their Traces
Invocations	Function wakes, cold starts, and the requests each wake served
Firewall	Mitigated requests and why the firewall acted

From the terminal, easel logs queries the same request stream:

easel logs --since 1h --status-code 5xx
easel logs --request-id <request-id> --expand
easel logs --follow

Build output isn't part of Observability. It lives with the deployment in Deployments. See Manage deployments.

Identifiers

These IDs link the views together. Copy them from the dashboard when you file a support request or correlate with your own logs.

ID	What it identifies
Request ID	One HTTP request. Clients receive it as `X-Easel-Id`.
Invocation ID	One function wake, which can serve more than one request
Deployment ID	The deployment that served the request

After a deploy

Observability doesn't draw deployment markers on charts. To check a release:

Note the deployment ID and the time it became Current.
Open Observability for a window that starts before that time, and compare errors, compute, cold starts, and bandwidth before and after.
When a chart moves, open Logs for the same window and filter by Deployment ID.
Open a failing or slow request and read its Trace.

Firewall rules, attack challenge mode, and deployment protection change traffic without a new deployment. If blocks or challenges spike, compare the time of the last change on the Firewall page with the spike. Environment variable changes apply only to new deployments. See Environment variables.

Export

Observability data is available in the dashboard and through easel logs. Easel doesn't offer log drains, an OTLP export endpoint, metrics export to third-party monitoring, observability webhooks, or archive connectors yet. OpenTelemetry spans flow into Easel Traces, not out of them.

To keep data beyond the retention window in Observability limits, send your application logs to your own system as well.

Next steps

Report a vulnerability

Report a potential security issue affecting Easel.

Requests

Find a request in Logs and read how Easel handled it, from firewall and cache to function work.