Hanzo
OpenapiO11y

Changes how one span field is stored — selects or deselects it as a…

Changes how one span field is stored — selects or deselects it as a materialized column and tunes its index — and echoes the setting back.

POST /v1/o11y/traces/fields

Addresshttps://api.hanzo.ai/v1/o11y/traces/fields
MethodPOST
OperationUpdateTraceField
AuthAuthorization: Bearer $HANZO_API_KEY

Changes how one span field is stored — selects or deselects it as a materialized column and tunes its index — and echoes the setting back.

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

Request

6 fields, body application/json (required).

FieldInTypeRequiredDescription
dataTypebodystringyesDataType is the field's data type, e.g.
indexbodystringIndex is the index expression to put on the column, e.g.
indexGranularitybodyintegerIndexGranularity is the index granularity in rows.
namebodystringyesName is the field to tune.
selectedbodybooleanSelected materializes the field as its own column when true.
typebodystringyesType is where the field lives: attributes or resources.

Response

StatusBodyMeaning
200o11y.O11yFieldSettingok

200 body — 6 fields.

FieldInTypeAlwaysDescription
dataTypebodystringyesDataType is the field's data type, e.g.
indexbodystringIndex is the index expression to put on the column, e.g.
indexGranularitybodyintegerIndexGranularity is the index granularity in rows.
namebodystringyesName is the field to tune.
selectedbodybooleanSelected materializes the field as its own column when true.
typebodystringyesType is where the field lives: attributes or resources.

Failure carries the platform error shape — see Errors.

Examples

hanzo o11y traces fields create \
  --data-type <dataType> \
  --name <name> \
  --type <type>

O11y API · All Hanzo APIs · Interactive reference

How is this guide?

On this page