Recent spans for your org over a time range
Answers `{count, spans}`, newest first, filtered on each span's START time.
GET /v1/metrics/traces/query
| Address | https://api.hanzo.ai/v1/metrics/traces/query |
| Method | GET |
| Operation | get_metrics_traces_query |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Answers {count, spans}, newest first, filtered on each span's START time. start and end are nanosecond bounds where 0 — which is what an absent, empty or unparseable value becomes — means UNBOUNDED, so a malformed bound widens the listing instead of failing it. limit defaults to 100 when absent or non-positive.
It lists SPANS, not traces: several spans of one trace each count separately and each take a slot against limit. Assembling one trace is /v1/metrics/traces/trace. The tenant is the gateway-minted X-Org-Id header, falling back to the deployment brand and then default.
Request
GET /v1/metrics/traces/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.
import { Configuration, MetricsApi } from 'hanzoai';
const api = new MetricsApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getMetricsTracesQuery();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_query()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.MetricsAPI.GetMetricsTracesQuery(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::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_query(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.MetricsApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new MetricsApi(client).getMetricsTracesQuery();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/metrics/traces/query \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches metrics through the metrics tool, which names its 11 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "get_log_health"
}
}
}'How is this guide?