Skip to content

Read request logs ​

Request logs answer operational questions that Analytics does not: which path returned a 404, whether a request reached the CDN, and which status a visitor received.

Use the console ​

Open https://app.edge.deca-dev.com/edge/{workspaceId}/logs, choose a distribution, and filter by time, method, status, host, or path text. Select a row to inspect it.

Rows include the timestamp, host, method, path, status, cache result, response bytes, environment, user agent, edge location, request id, the visitor's IP address (client_ip), and their country. They never include the query string, cookies, or request body. Analytics never stores the IP address.

A 403 with edge_result FunctionGeneratedResponse was refused at the edge, usually by a network rule; the row pane says so.

Ask an agent, use the CLI, or call the API ​

text
Show 404 and 500-level requests for acme-marketing from the last hour.
bash
edge api GET /v1/logs?distribution_id=d3f7a1c4-90b2-4e6a-8f15-6c2b7e0a9d38&from=2026-09-24T00:00:00Z&status_class=5&limit=50
bash
curl -s \
  "https://api.edge.deca-dev.com/v1/logs?distribution_id=d3f7a1c4-90b2-4e6a-8f15-6c2b7e0a9d38&from=2026-09-24T00:00:00Z&status_class=5&limit=50" \
  -H "Authorization: Bearer $EDGE_TOKEN"

The agent runs edge_log_list. The default range is the last hour and a page contains at most 50 rows. Use the returned cursor for the next page. Run edge_log_get or GET /v1/logs/{id} to inspect one row by id.

Use status=404 for one exact status or status_class=5 for all 5xx responses. q searches the path text; it does not search a hidden query string. ip takes an address or a range (ip=203.0.113.0/24, ip=2001:db8::/32) and country a two-letter code (country=JP).

Understand retention ​

The most recent seven days come from the hot store and are suitable for live investigation. Older request logs are not queryable yet: requests for that range return 503 rather than partial results.

Function stdout and stderr are a different log stream. See Function runtimes.

Next ​