Skip to main content
Create a root key with the permissions listed on this page under Root Keys in the dashboard sidebar. CLI commands can instead use a session from unkey login with the required permissions. See Permission reference for every permission.
Run a SQL query against the logs your deployments wrote. Query the runtime_logs_v1 table. CTEs, subqueries, UNION, and EXCEPT all work. You only see data from the root key’s workspace. To narrow it to one , , , or deployment, filter on project_id, app_id, environment_id, or deployment_id. Your plan’s log query range limits how far back a query can reach, and analytics query quotas apply. See Limits.

Usage

Flags

string
required
SQL query to run against runtime_logs_v1.

Shared flags

Every resource command accepts these; CLI output and shared flags describes them in full.
string
A JSON document sent as the request body instead of building it from the flags above. It is mutually exclusive with the request-building flags, and unknown fields are rejected locally. See Send a raw body.
string
Root key used for the request. Falls back to UNKEY_ROOT_KEY, then stored credentials, including a CLI session. See CLI authentication for the full precedence order.
string
default:"https://api.unkey.com"
Base URL of the API. Falls back to UNKEY_API_BASE_URL. You don’t normally need to set it.
string
default:"~/.unkey/config.toml"
Path of the TOML config file. Falls back to UNKEY_CONFIG. An explicit --config takes precedence over a stored CLI session. Browser login stores a session, not a root key in this file. See CLI authentication.
enum
default:"human"
Use human (default) for name-first summary tables and single-response trees, or json for the unchanged full response envelope, including all fields and pagination. Trees wrap long values without truncation. Terminal tables use relative timestamps and may shorten display names and descriptions, but never identifiers, slugs, or credentials. Redirected human output keeps complete values and uses RFC3339 UTC timestamps. Falls back to UNKEY_OUTPUT; other values are rejected. --json also selects JSON output. Add --debug to print the request ID to stderr. See Output formats.
boolean
Print the successful response’s request ID to stderr, separate from stdout.
boolean
Print the full response as JSON. Takes precedence over a valid --output or UNKEY_OUTPUT value.

Required permissions

Your root key needs project.*.read_runtime_logs. A grant for one project, such as project.<project_id>.read_runtime_logs, doesn’t work here. Without a matching permission the API answers 403 and the CLI prints Permission denied: followed by the detail. See Root key permissions for the full catalog.

Examples

Latest log lines of one deployment:
Count lines by severity:
Send the request body as JSON:

API endpoint

The command calls POST /v2/analytics.getRuntimeLogs and prints its response. The request fields carry the same names as the flags in camelCase, which is the shape --body expects.

Analytics tables

Column reference for gateway request and runtime log analytics.
Last modified on October 28, 2026