errors.traces.get

Read a trace: its transactions and spans on one time axis, and the errors in it

GET /errors/api/traces/{traceId}IAM errors:GetEventsRead

Request syntax

GET /errors/api/traces/{traceId}

Path parameters

  • traceIdRequired

    string

    Constraints: /^[0-9a-fA-F]{32}$/

Response

200 with the trace in the projects whose events you may read: traceId; `transactions` (eventId, projectId, projectName, name, op, status, durationMs, spanCount, release, environment, measurements); `errors` (eventId, issueId, shortId, title); `rows`, the waterfall (id, depth, kind transaction|span, op, label, status, offsetMs from the trace start, durationMs, transactionEventId, projectId, errors); durationMs and startMs of the whole trace; `hidden`, rows of projects you may not read; `profiled`, the event ids of transactions with a profile. 404 when none of it is in a project you may read.

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 traces get traceId

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