Reports whether a product's service is live: an in-cluster health probe with…
Reports whether a product's service is live: an in-cluster health probe with its measured latency, fused with the per-replica up inventory.
GET /v1/o11y/status
| Address | https://api.hanzo.ai/v1/o11y/status |
| Method | GET |
| Operation | get_o11y_status |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Reports whether a product's service is live: an in-cluster health probe with its measured latency, fused with the per-replica up inventory. Infra health is not tenant-partitioned — a service is up or down for everyone — so any validated caller is served, but an unvalidated one is refused. A product with no backing workload answers down/unknown-service without probing anything; a malformed slug is a 400.
Request
1 field.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
product | query | string | — | Product is the console product slug to probe, e.g. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | o11y.statusResult | ok |
200 body — 8 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
checkedAt | body | string | — | CheckedAt is when this answer was measured, RFC3339 UTC. |
deployments | body | o11y.deployment[] | — | Deployments is the per-replica inventory behind the verdict. |
deployments[].instance | body | string | — | Instance is the replica as the telemetry store labels it — the address the series was recorded against, which is what distinguishes two replicas of one service. |
deployments[].up | body | boolean | — | Up is that replica's last reported state. Every target emits on every cycle, so a replica missing from the list is one the prober is not reporting at all,… |
latencyMs | body | integer | — | LatencyMs is the health probe's round trip in MILLISECONDS, time-boxed at two seconds. |
product | body | string | — | Product is the service this answer is about, echoed back. |
source | body | string | — | Source is where the verdict came from: "probe" (we asked and it answered), "datastore" (the probe did not answer and the replica inventory decided it),… |
up | body | boolean | — | Up is true when the health probe succeeded OR any replica reports up, so a service reachable by either route reads up. |
Failure carries the platform error shape — see Errors.
Examples
hanzo o11y statusimport { Configuration, O11yApi } from 'hanzoai';
const api = new O11yApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getO11yStatus();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).get_o11y_status()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.O11yAPI.GetO11yStatus(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::get_o11y_status(&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).getO11yStatus();curl https://api.hanzo.ai/v1/o11y/status \
-H "Authorization: Bearer $HANZO_API_KEY"Tool o11y, op get_o11y_status — POST the JSON-RPC envelope to https://api.hanzo.ai/v1/mcp.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "o11y",
"arguments": {
"op": "get_o11y_status",
"input": {}
}
}
}'How is this guide?