OpenapiO11y
Promotes and indexes log body paths: each named path is lifted out of the JSON…
Promotes and indexes log body paths: each named path is lifted out of the JSON body into its own column, with the indexes the caller asked for.
POST /v1/o11y/logs/promote_paths
| Address | https://api.hanzo.ai/v1/o11y/logs/promote_paths |
| Method | POST |
| Operation | post_o11y_logs_promote_paths |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Promotes and indexes log body paths: each named path is lifted out of the JSON body into its own column, with the indexes the caller asked for. Paths must start with "body.".
Callers need the editor role; the runtime's own gate enforces it.
Request
6 fields, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
[].indexes | body | o11y.O11yLogPromoteIndex[] | — | Indexes are the indexes to put on the path. |
[].indexes[].fieldDataType | body | string | — | FieldDataType is the path's data type, e.g. |
[].indexes[].granularity | body | integer | — | Granularity is the index granularity in rows. |
[].indexes[].type | body | string | — | Type is the index type, e.g. |
[].path | body | string | — | Path is the body path, e.g. |
[].promote | body | boolean | — | Promote lifts the path into its own column when true. |
Response
| Status | Body | Meaning |
|---|---|---|
201 | o11y.O11yLogPromoteOut | created |
201 body — 1 field.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
status | body | string | — | Status is "success". |
Failure carries the platform error shape — see Errors.
Examples
hanzo o11y logs promote_paths createimport { Configuration, O11yApi } from 'hanzoai';
const api = new O11yApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postO11yLogsPromotePaths();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_logs_promote_paths()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.O11yAPI.PostO11yLogsPromotePaths(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_logs_promote_paths(&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).postO11yLogsPromotePaths();curl -X POST https://api.hanzo.ai/v1/o11y/logs/promote_paths \
-H "Authorization: Bearer $HANZO_API_KEY"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?