List metric metadata

Serves the OLDER /metric/metric_metadata route.

GET /v1/o11y/metric/metric_metadata

O11y → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/o11y/metric/metric_metadata`
Method	`GET`
Operation	`get_o11y_metric_metric_metadata`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Serves the OLDER /metric/metric_metadata route. It is NOT the same op as metrics.go's metricMetadata (/metrics/metadata): different path, different input (this one also scopes by service). Two slices named one Go function for two routes; the route is the identity, so the name follows it. Renamed rather than merged — collapsing them would silently drop the service scope this one accepts. It returns one metric's metadata — its type, unit, description, temporality, monotonicity and histogram buckets — optionally scoped to the metric as one service reports it.

Callers need the viewer role; the runtime's own gate enforces it.

Request

2 fields.

Field	In	Type	Required	Description
`metricName`	query	string	—	MetricName is the metric to read.
`serviceName`	query	string	—	ServiceName scopes the metadata to the metric as one service reports it.

Response

Status	Body	Meaning
`200`	o11y.O11yMetricMetadataOut	ok
`202`	Approval	held for approval
`default`	problem-details	refused

200 body — 7 fields.

Field	In	Type	Always	Description
`data`	body	o11y.O11yMetricMetadata	—
`data.description`	body	string	—	Description describes the metric.
`data.isMonotonic`	body	boolean	—	IsMonotonic marks a sum that only ever increases.
`data.temporality`	body	string	—	Temporality is delta or cumulative.
`data.type`	body	string	—	Type is the metric type, e.g. gauge, sum, histogram.
`data.unit`	body	string	—	Unit is the metric's unit.
`status`	body	string	—	Status is "success".

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo o11y metric metric_metadata

.ts

.py

.go

.rs

.java

import { Configuration, O11yApi } from 'hanzoai';

const api = new O11yApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getO11yMetricMetricMetadata();

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_metric_metric_metadata()

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.O11yAPI.GetO11yMetricMetricMetadata(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::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_metric_metric_metadata(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.O11yApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new O11yApi(client).getO11yMetricMetricMetadata();

curl https://api.hanzo.ai/v1/o11y/metric/metric_metadata \
  -H "Authorization: Bearer $HANZO_API_KEY"

Tool o11y, op get_o11y_metric_metric_metadata — 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_metric_metric_metadata",
           "input": {}
         }
       }
     }'

O11y API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList logs — GET /v1/o11y/logs NextList attribute keys — GET /v1/o11y/namespaces/attribute_keys