List trace

Answers {spans}: every span the org holds for the trace id in id, in the order they were appended, which is what a waterfall view renders.

GET /v1/metrics/traces/trace

Addresshttps://api.hanzo.ai/v1/metrics/traces/trace
MethodGET
Operationget_metrics_traces_trace
AuthAuthorization: Bearer $HANZO_API_KEY

Answers {spans}: every span the org holds for the trace id in id, in the order they were appended, which is what a waterfall view renders. Unlike the other reads there is no count, no time range and no limit — a trace is addressed by id or not at all.

An id with no spans answers an EMPTY list, never a 404: the store cannot tell a trace that never existed from one whose spans retention has already dropped, so it does not pretend to. The tenant is the gateway-minted X-Org-Id header, falling back to the deployment brand and then default, and a trace id belonging to another org is simply not in this org's store.

Request

GET /v1/metrics/traces/trace 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 metrics traces trace
import { Configuration, MetricsApi } from 'hanzoai';

const api = new MetricsApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getMetricsTracesTrace();
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import MetricsApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = MetricsApi(client).get_metrics_traces_trace()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.MetricsAPI.GetMetricsTracesTrace(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, metrics_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = metrics_api::get_metrics_traces_trace(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.MetricsApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new MetricsApi(client).getMetricsTracesTrace();
curl https://api.hanzo.ai/v1/metrics/traces/trace \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP declares no tool for metrics — tools/list on https://api.hanzo.ai/v1/mcp names the products it does reach. Use HTTP or an SDK.


Metrics API · All Hanzo APIs · Interactive reference

Was this page useful?