OpenapiO11y
Returns one service's entry-point operations with the same latency and error…
Returns one service's entry-point operations with the same latency and error profile topOperations reports.
POST /v1/o11y/service/entry_point_operations
| Address | https://api.hanzo.ai/v1/o11y/service/entry_point_operations |
| Method | POST |
| Operation | post_o11y_service_entry_point_operations |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Returns one service's entry-point operations with the same latency and error profile topOperations reports.
Request
11 fields, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
end | body | string | — | End is the window's end, epoch nanoseconds as a string. |
limit | body | integer | — | Limit caps how many operations come back. |
service | body | string | — | Service is the service whose operations are read. |
start | body | string | — | Start is the window's start, epoch nanoseconds as a string. |
tags | body | o11y.O11yServiceTag[] | — | Tags narrow the spans counted, each a span-attribute predicate. |
tags[].BoolValues | body | boolean[] | — | BoolValues are the boolean operands, when the attribute is a bool. |
tags[].Key | body | string | — | Key is the span attribute to test. |
tags[].NumberValues | body | number[] | — | NumberValues are the numeric operands, when the attribute is a number. |
tags[].Operator | body | string | — | Operator is how to test it, e.g. |
tags[].StringValues | body | string[] | — | StringValues are the string operands, when the attribute is a string. |
tags[].TagType | body | string | — | TagType says which plane the attribute lives on, e.g. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | o11y.O11yOperationsOut | ok |
200 body — 8 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
data | body | o11y.O11yOperation[] | — | Data holds one entry per operation. |
data[].errorCount | body | integer | — | ErrorCount is how many of those runs errored. |
data[].name | body | string | — | Name is the operation (span name). |
data[].numCalls | body | integer | — | NumCalls is how many times it ran in the window. |
data[].p50 | body | number | — | P50 is its median latency, nanoseconds. |
data[].p95 | body | number | — | P95 is its p95 latency, nanoseconds. |
data[].p99 | body | number | — | P99 is its p99 latency, nanoseconds. |
status | body | string | — | Status is "success". |
Failure carries the platform error shape — see Errors.
Examples
hanzo o11y service entry_point_operationsimport { Configuration, O11yApi } from 'hanzoai';
const api = new O11yApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postO11yServiceEntryPointOperations({ end: "<end>", limit: 0 });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import O11yApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = O11yApi(client).post_o11y_service_entry_point_operations(end="<end>", limit=0)cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.O11yAPI.PostO11yServiceEntryPointOperations(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, o11y_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = o11y_api::post_o11y_service_entry_point_operations(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.O11yApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new O11yApi(client).postO11yServiceEntryPointOperations();curl -X POST https://api.hanzo.ai/v1/o11y/service/entry_point_operations \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"end": "<end>",
"limit": 0
}'The door reaches o11y through the o11y tool, which names its 340 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_o11y_alert_last"
}
}
}'How is this guide?