Hanzo
OpenapiO11y

Lists the traces a project's captured errors reference, each with how many…

Lists the traces a project's captured errors reference, each with how many errors landed on it, when they started and stopped, and the latest message seen…

GET /v1/o11y/sentinel/traces

Addresshttps://api.hanzo.ai/v1/o11y/sentinel/traces
MethodGET
Operationget_o11y_sentinel_traces
AuthAuthorization: Bearer $HANZO_API_KEY

Lists the traces a project's captured errors reference, each with how many errors landed on it, when they started and stopped, and the latest message seen — the entry point for "which requests are failing".

Request

3 fields.

FieldInTypeRequiredDescription
projectquerystringyesProject is the project to read, as its id.
periodquerystringPeriod is the window to read, relative to now — 1h, 24h, 7d, 14d, 30d.
limitqueryintegerLimit caps how many traces come back.

Response

StatusBodyMeaning
200o11y.O11yTracesOutok

200 body — 8 fields.

FieldInTypeAlwaysDescription
databodyo11y.O11yTraces
data.itemsbodyo11y.O11yTrace[]Items are the traces, most recent first.
data.items[].countbodyintegerCount is how many captured errors carried it.
data.items[].firstSeenbodystring (date-time)FirstSeen is when the earliest of them was recorded.
data.items[].lastSeenbodystring (date-time)LastSeen is when the latest was.
data.items[].messagebodystringMessage is the latest error message seen on the trace.
data.items[].traceIdbodystringTraceID is the trace id.
statusbodystringStatus is "success".

Failure carries the platform error shape — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.


O11y API · All Hanzo APIs · Interactive reference

How is this guide?

On this page