Hanzo
OpenapiMetrics

Search your org's logs by label, time and substring

Answers `{count, records}`, newest first. `match` is the same `k=v,k2=v2` superset label matcher the metrics query uses; `contains` is a case-insensitive…

GET /v1/metrics/logs/query

Addresshttps://api.hanzo.ai/v1/metrics/logs/query
MethodGET
Operationget_metrics_logs_query
AuthAuthorization: Bearer $HANZO_API_KEY

Answers {count, records}, newest first. match is the same k=v,k2=v2 superset label matcher the metrics query uses; contains is a case-insensitive substring test against the record body; start and end are nanosecond bounds.

A bound that is absent, empty or unparseable becomes 0, which means UNBOUNDED — a malformed start widens the search rather than failing it. limit caps the page and defaults to 100 when absent or non-positive, so an unfiltered read is never the whole ring.

The tenant is the gateway-minted X-Org-Id header, falling back to the deployment brand and then default, so a search can only reach the org the edge asserted.

Request

GET /v1/metrics/logs/query takes no parameters and no body — the credential is the whole request.

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — 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.


Metrics API · All Hanzo APIs · Interactive reference

How is this guide?

On this page