Skip to main content
Observe

Observability

Understand application behavior across deployments, requests, functions, cache, and security events.

Easel observability connects each incoming request to the deployment, route, cache decision, function execution, and security action that handled it.

Use observability to answer questions such as:

  • Which deployment served this request?
  • Did the response come from cache?
  • Which route matched?
  • Did a function run?
  • Was the function cold or warm?
  • Did a firewall rule block or challenge it?
  • Where did the request spend time?
  • Did the failure happen during build, routing, or runtime?

Surfaces

Open a project and use these dashboard views:

SurfaceUse it for
ObservabilityTraffic, bandwidth, function starts, compute, and custom queries over time
LogsIndividual requests, function log lines, and per-request Traces
InvocationsMultiplexed function wakes, cold starts, and AWS billing fields

From the terminal, use easel logs to query and follow the same request stream.

Observability model

Easel organizes observability around related data types:

  • Requests describe an incoming HTTP request and its final response.
  • Logs contain application and platform-generated messages for a request.
  • Metrics aggregate behavior over time on Observability charts.
  • Traces connect edge routing, function work, and application OpenTelemetry spans for one request.
  • Invocations describe a function wake that may serve multiple requests.
  • Security signals explain firewall and access-control decisions when available.
  • Deployment activity lives primarily in Deployments and build logs, with filters that let you scope Observability to a deployment.

These signals share stable identifiers such as request ID and invocation ID so you can move from a chart to an individual request and then to its Trace.

Request lifecycle

A request may pass through several stages:

Client request

Security evaluation

Domain and deployment routing

Cache lookup

Static response, middleware, or function

Response

Security controls run before cache and application execution. See Security evaluation order.

Start here

On this page

Edit on GitHub