OpenapiO11y
Lists the attribute keys available for filtering the given telemetry, each with…
Lists the attribute keys available for filtering the given telemetry, each with its data type and whether it is a materialized column.
GET /v1/o11y/autocomplete/attribute_keys
| Address | https://api.hanzo.ai/v1/o11y/autocomplete/attribute_keys |
| Method | GET |
| Operation | get_o11y_autocomplete_attribute_keys |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Lists the attribute keys available for filtering the given telemetry, each with its data type and whether it is a materialized column.
Callers need the viewer role; the runtime's own gate enforces it.
Request
6 fields.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
dataSource | query | string | — | DataSource is the telemetry the keys come from — traces, logs, metrics or meter. |
aggregateOperator | query | string | — | AggregateOperator is the aggregation the keys will be used under. |
aggregateAttribute | query | string | — | AggregateAttribute is the metric the keys must appear on. |
searchText | query | string | — | SearchText narrows the keys to those containing it. |
tagType | query | string | — | TagType narrows the keys to one kind — tag or resource. |
limit | query | integer | — | Limit caps how many keys come back. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | o11y.O11yAttributeKeysOut | ok |
200 body — 8 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
data | body | o11y.FilterAttributeKeyResponse | — | |
data.attributeKeys | body | o11y.AttributeKey[] | — | |
data.attributeKeys[].dataType | body | string | — | |
data.attributeKeys[].isColumn | body | boolean | — | |
data.attributeKeys[].isJSON | body | boolean | — | |
data.attributeKeys[].key | body | string | — | |
data.attributeKeys[].type | body | string | — | |
status | body | string | — | Status is "success". |
Failure carries the platform error shape — see Errors.
Examples
hanzo o11y autocomplete attribute_keysimport { Configuration, O11yApi } from 'hanzoai';
const api = new O11yApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getO11yAutocompleteAttributeKeys();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_autocomplete_attribute_keys()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.O11yAPI.GetO11yAutocompleteAttributeKeys(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_autocomplete_attribute_keys(&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).getO11yAutocompleteAttributeKeys();curl https://api.hanzo.ai/v1/o11y/autocomplete/attribute_keys \
-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?