errors.queries.list-all

List every statement: measured by the connected databases (every call) and seen in traces, joined by fingerprint

GET /errors/api/projects/{id}/queries/allIAM errors:GetEventsRead

Each row says its source: both, database (background jobs, migrations, other apps, or not sampled) or traces (a database that is not connected). A connected database counts only when the caller has rds:DescribeDBQueryInsights on it; text is pg_stat_statements’ normalised form, never values or plans.

Without rds:DescribeDBQueryInsights the answer is reduced rather than refused.

Request syntax

GET /errors/api/projects/{id}/queries/all

Path parameters

  • idRequired

    string

    Constraints: uuid

Query parameters

  • rangeOptional

    enum

    Window counted back from now: the last 24 hours (default) or 7 days

    One of: 24h, 7d

    Default: "24h"

  • roleOptional

    enum

    app: only the statements of the roles of the apps connected to this project (the default when each has its own role); all: every statement of the database

    One of: app, all

  • limitOptional

    number

    Most statements to return, by total time spent across the databases and the traces: 1–200, default 50 (the console shows up to 200)

    Constraints: integer, 1-200

    Default: 50

Response

200 with { range, links, appRoles, roleFilterAvailable, role, rows, tracesHaveDbSpans }: `links` the connected databases as `databases list` gives them; `appRoles` the Postgres roles of the project’s connected apps on the databases you may read (dbInstanceId, roleName, appName); `role` the scope applied (`all` whenever `roleFilterAvailable` is false, that is when an app uses the master user, whatever you asked); `rows` by total time, each with fingerprint, statement, source (both, database or traces), calls, totalMs, meanMs, maxMs, rows (returned rows, null for traces only), share (of all the time listed, 0–1), places (dbInstanceId, database, role, calls), series (the database’s totalMs and calls per bucket) and traces (calls, totalMs, transactions, nPlusOne, lastSeen; null when no sampled transaction ran it). The numbers are the database’s when it measured the statement, else the traces’. 404 when the project does not exist, 403 without errors:GetEvents on it.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow errors:GetEvents on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud errors queries list-all id

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_errors_queries_list-all.