> ## Documentation Index
> Fetch the complete documentation index at: https://unkey.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> Unkey is two separate products. Compute builds, deploys, and runs apps behind a gateway. API Management issues API keys, enforces rate limits, manages identities and permissions, and reports usage. Say which product a page belongs to; a reader can use either without the other.
> Every Unkey API endpoint is an HTTP POST to https://api.unkey.com/v2/{service}.{procedure} with a root key in the Authorization: Bearer header. Root keys are workspace scoped.
> Error codes have the form err:{system}:{category}:{specific} and each has a page at /errors/{system}/{category}/{specific}.
> The word environment means production or preview in Compute. Rate limiting has four meanings on this site; the glossary lists them.
# Query gateway requests and runtime logs
> Query gateway requests and runtime logs with SQL through the analytics API.
export const ProductLink = ({product, href, title, children}) => {
const productNames = {
compute: "Compute",
"api-management": "API Management",
platform: "Platform"
};
return
;
};
The SQL you can use, query quotas, and query errors are documented in API Management. Here we cover the two Compute tables.
You can query your app's [request log](/docs/compute/observe/requests) and [runtime logs](/docs/compute/observe/runtime-logs) with SQL, to build your own dashboards, alerts, or exports. Each table has its own endpoint and permission.
| Table | Endpoint | Root key permission |
| - | - | - |
| `gateway_requests_v1` | `POST /v2/analytics.getGatewayRequests` | `project.*.read_gateway_requests` |
| `runtime_logs_v1` | `POST /v2/analytics.getRuntimeLogs` | `project.*.read_runtime_logs` |
You need a root key with the wildcard (`project.*`) permission for the table. A permission for a single project doesn't work here. Create the key under **Settings > Root Keys** and send it as `Authorization: Bearer `. See [Root keys](/docs/platform/root-keys/overview).
## Query rules
* Only `SELECT` runs. CTEs, subqueries, `UNION`, and `EXCEPT` are fine.
* You only ever see your own workspace's data. To narrow further, filter on `project_id`, `app_id`, or `environment_id`.
* The time range can't reach back further than your plan's log query range (3 days on Starter, 7 on Pro, 14 on Business), or the query fails with [`query_range_exceeds_retention`](/docs/errors/user/bad_request/query_range_exceeds_retention). See [Compute limits](/docs/compute/configure/limits#log-query-range).
* A result larger than 4 MiB fails with [`query_memory_limit_exceeded`](/docs/errors/user/unprocessable_entity/query_memory_limit_exceeded).
The response is `{"meta":{"requestId":...},"data":[...]}` with one object per row.
## Examples
```bash curl theme={"system"}
curl -X POST https://api.unkey.com/v2/analytics.getGatewayRequests \
-H "Authorization: Bearer $UNKEY_ROOT_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"SELECT path, count() AS total FROM gateway_requests_v1 WHERE response_status >= 500 AND time >= toUnixTimestamp64Milli(now64(3) - INTERVAL 24 HOUR) GROUP BY path ORDER BY total DESC LIMIT 10"}'
```
```bash CLI theme={"system"}
unkey api analytics get-gateway-requests \
--query="SELECT path, count() AS total FROM gateway_requests_v1 WHERE response_status >= 500 AND time >= toUnixTimestamp64Milli(now64(3) - INTERVAL 24 HOUR) GROUP BY path ORDER BY total DESC LIMIT 10"
```
```bash curl theme={"system"}
curl -X POST https://api.unkey.com/v2/analytics.getRuntimeLogs \
-H "Authorization: Bearer $UNKEY_ROOT_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"SELECT time, severity, message FROM runtime_logs_v1 WHERE lower(message) LIKE '"'"'%timeout%'"'"' ORDER BY time DESC LIMIT 100"}'
```
```bash CLI theme={"system"}
unkey api analytics get-runtime-logs \
--query="SELECT time, severity, message FROM runtime_logs_v1 WHERE lower(message) LIKE '%timeout%' ORDER BY time DESC LIMIT 100"
```
`time` is a Unix timestamp in milliseconds in both tables, so the examples compare it with `toUnixTimestamp64Milli(...)`.
## gateway\_requests\_v1
One row per request that reached your app. Requests a policy rejected aren't here. See [Request logs](/docs/compute/observe/requests).
The request ID, also sent as `X-Unkey-Request-Id`.Unix timestamp in milliseconds when the gateway received the request.Your workspace, the one the root key belongs to.The project.The app.The environment.The deployment that served the request.The instance that served the request.The region of the gateway that served the request.Upper-case HTTP method.The requested hostname.The request path without the query string.The raw query string. Empty unless a logging policy captured query data.Parsed query parameters. Empty unless a logging policy captured query data.`Key: Value` strings. Empty unless a logging policy captured request headers. API keys are redacted.Up to 1 MiB. Empty unless a logging policy captured the request body.The status the client received.`Key: Value` strings. Empty unless a logging policy captured response headers.Up to 1 MiB. Empty unless a logging policy captured the response body.Empty unless a logging policy captured request headers.The client IP. Empty unless a logging policy captured request headers.Milliseconds from receipt to the end of the response.Milliseconds spent by your instance.`total_latency` minus `instance_latency`.
## runtime\_logs\_v1
One row per log line from your instances. Structured attributes are in `attributes_text`, as a JSON string.
Stable identifier of the log line.Unix timestamp in milliseconds when the line was written.Unix timestamp in milliseconds when the line was stored. Filter on it as well as on `time` to make queries over a wide range faster.Lower-case severity parsed from the line, `info` when none was found.The message, with color codes removed.Your workspace.The project.The environment.The app.The deployment whose instance wrote the line.The region the instance ran in.The parsed attributes as a JSON string. Search it with `lower(attributes_text) LIKE '%...%'`, which the table indexes.