Skip to content

Commit eb7b538

Browse files
committed
Describe edge logs as requests handled at the edge, with their query limits
1 parent 2edde49 commit eb7b538

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎content/cli/storage.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ With `--json`, `data` carries `deleted`.
8484

8585
Read a Space's logs.
8686

87-
`access` is every request that reached your Space's origin. `edge` is every request the edge served, cache hits included; see [Edge request logs](/infrastructure/edge-request-logs) for its filters. `runtime` is what your code logged, with the request id and handler for each line. A static Space has no runtime lines.
87+
`access` covers requests that reached your Space's origin. `edge` covers requests handled at the edge, cache hits included. Each edge query reads one hostname (the primary unless you pass `--hostname`), and a busy window can be truncated; see [Edge request logs](/infrastructure/edge-request-logs) for its filters and limits. With `runtime` you get what your code logged, with the request id and handler for each line. A static Space has no runtime lines.
8888

8989
A line you just triggered takes a while to appear — it's written on the origin, shipped, and indexed before it can be read back. **An empty page means not yet, not broken.** Keep paging while the cursor is there: a page can come back empty while there's still more to read.
9090

0 commit comments

Comments
 (0)