Claude Platform Docs

Назначения телеметрии

Создание назначения телеметрии
$ ant beta:organization:telemetry-destinations create
POST/v1/organizations/telemetry_destinations

Зарегистрировать назначение OpenTelemetry для организации.

Список назначений телеметрии
$ ant beta:organization:telemetry-destinations list
GET/v1/organizations/telemetry_destinations

Получить список назначений организации, начиная с самых новых, с возможностью ограничиться только теми, которые охватывают указанные рабочие пространства.

Получение назначения телеметрии
$ ant beta:organization:telemetry-destinations retrieve
GET/v1/organizations/telemetry_destinations/{destination_id}

Прочитать конфигурацию назначения, его состояние и последние результаты доставки.

Обновление назначения телеметрии
$ ant beta:organization:telemetry-destinations update
POST/v1/organizations/telemetry_destinations/{destination_id}

Изменить параметры назначения телеметрии, его состояние или охватываемые им рабочие пространства.

Удаление назначения телеметрии
$ ant beta:organization:telemetry-destinations delete
DELETE/v1/organizations/telemetry_destinations/{destination_id}

Удалить назначение и его список рабочих пространств.

Тестирование назначения телеметрии
$ ant beta:organization:telemetry-destinations test
POST/v1/organizations/telemetry_destinations/{destination_id}/test

Отправить в назначение один тестовый спан с именем anthropic.test с его зарегистрированными заголовками, однократно и без повторных попыток, и сообщить ответ назначения. Ответ имеет код 200 независимо от того, ответило ли назначение статусом 2xx: его result имеет тип success либо тип failure с причиной в error. Конфигурация назначения, state и delivery_health не изменяются. Отключённое назначение также можно протестировать. Выдерживайте 10 секунд между тестами одного назначения; на запрос, поступивший раньше, может быть получен ответ со статусом 429.

Models
beta_deleted_telemetry_destination: object{ type: "telemetry_destination_deleted", id }

Confirmation that a destination was deleted.

type: "telemetry_destination_deleted"
id: string

ID of the deleted destination (tdst_...).

beta_telemetry_destination: object{ type: "telemetry_destination", id, created_at, 8 more }

An OpenTelemetry destination: an OTLP/HTTP endpoint, the request headers sent with every delivery to it, what the exported spans contain, and which workspaces it covers. A destination belongs to an organization. A workspace's spans go to every enabled destination that covers it.

beta_telemetry_destination_content_mode: "metadata_only" or "content"

What the spans that the API exports to a telemetry destination contain.

See the OpenTelemetry export guide to learn what the spans contain in each content mode.

"metadata_only"

The spans contain identifiers, timing, status, token counts, and similar metadata. They don't contain prompt text, completion text, or tool inputs and outputs.

"content"

The spans contain the same metadata as metadata_only, plus message and tool content.

An organization with a data-handling restriction, such as under HIPAA, can't choose this mode. The API exports only metadata for such an organization, even to a destination that already has content.

beta_telemetry_destination_delivery_health: object{ last_error, last_error_at, last_success_at }

The most recent delivery results that the API records for a telemetry destination.

Changes to the destination's configuration or state don't reset these fields. Changes to these fields don't change updated_at. The values can lag behind the latest deliveries.

See the OpenTelemetry export guide to learn how the API delivers spans and when it disables a destination.

last_error: string

A message that describes the most recent failed delivery to the destination, or null if no delivery has failed yet.

Examples are temporary DNS failure, TLS failure, timeout, connection failure, invalid address, HTTP error (status 503), and redirect (status 301). The message is invalid address both for a hostname that doesn't exist and for an address that isn't publicly routable. It never contains the endpoint's response body, a header value, a network address, or TLS details.

last_error and last_error_at always change together. A later successful delivery doesn't clear them. If last_success_at is later than last_error_at, a delivery has succeeded since this failure.

See the OpenTelemetry export guide to learn the likely cause of each error.

last_error_at: string

Time of the failure that last_error describes. Changes together with last_error. Null until a delivery first fails.

formatdate-time
last_success_at: string

Time of the most recent successful delivery to the destination, or null if no delivery has succeeded yet.

formatdate-time
beta_telemetry_destination_disabled_reason: BetaTelemetryDestinationDisabledReasonCaller or BetaTelemetryDestinationDisabledReasonSustainedFailure or BetaTelemetryDestinationDisabledReasonInvalidAddress or BetaTelemetryDestinationDisabledReasonRedirect

Why the destination is disabled: caller when a caller disabled it, or the reason the API disabled it automatically (sustained_failure, invalid_address, or redirect). Every automatic disable is reversible with an update that sets state to enabled. An update that sets disabled on a destination that is already disabled keeps its reason.

beta_telemetry_destination_disabled_reason_caller: object{ type: "caller" }

A caller disabled the destination with an update that set state to disabled.

type: "caller"
beta_telemetry_destination_disabled_reason_invalid_address: object{ type: "invalid_address" }

The API disabled the destination because deliveries to it failed for longer than the same threshold as for sustained_failure, and the most recent failed delivery failed with an invalid address: the DNS answer says that the endpoint's hostname doesn't exist or doesn't have an address, or the address that the API would connect to isn't publicly routable or is reserved, for example a loopback, link-local, private-network, or cloud-metadata address. The API doesn't connect to such an address, and retries the delivery a bounded number of times as it does after a timeout. A timeout or a server failure of the DNS lookup is a temporary DNS failure instead, not an invalid address.

type: "invalid_address"
beta_telemetry_destination_disabled_reason_redirect: object{ type: "redirect" }

The API disabled the destination because the endpoint answered a delivery with a 3xx status. Redirects are never followed, and one such answer disables the destination at once.

type: "redirect"
beta_telemetry_destination_disabled_reason_sustained_failure: object{ type: "sustained_failure" }

The API disabled the destination because deliveries to it failed, with no successful delivery in between, for longer than a threshold that Anthropic configures and that is not part of this contract. The reason is invalid_address instead when the most recent failed delivery failed with an invalid address.

type: "sustained_failure"
beta_telemetry_destination_state: BetaTelemetryDestinationStateEnabled or BetaTelemetryDestinationStateDisabled

Whether a telemetry destination receives deliveries.

A caller can set either state. The API also disables an enabled destination on its own in some cases. The reason of the disabled state says whether a caller or the API disabled the destination and, when the API did, why.

See the OpenTelemetry export guide to learn when the API disables a destination.

beta_telemetry_destination_state_disabled: object{ type: "disabled", reason }

The API doesn't deliver anything to the telemetry destination.

Spans produced while it is disabled aren't delivered later.

beta_telemetry_destination_state_disabled_params: object{ type: "disabled" }

Stop deliveries to the telemetry destination.

Spans produced while it is disabled aren't delivered later. A destination that is already disabled keeps its reason.

type: "disabled"
beta_telemetry_destination_state_enabled: object{ type: "enabled" }

The telemetry destination receives the spans of the workspaces that it covers.

type: "enabled"
beta_telemetry_destination_state_enabled_params: object{ type: "enabled" }

Start deliveries to the telemetry destination again.

This doesn't reset delivery_health.

type: "enabled"
beta_telemetry_destination_state_params: BetaTelemetryDestinationStateEnabledParams or BetaTelemetryDestinationStateDisabledParams

The state to set on a telemetry destination, by type alone.

A caller can't set the reason of a disabled state. Only the API sets it.

beta_telemetry_destination_state_enabled_params: object{ type: "enabled" }

Start deliveries to the telemetry destination again.

This doesn't reset delivery_health.

type: "enabled"
beta_telemetry_destination_state_disabled_params: object{ type: "disabled" }

Stop deliveries to the telemetry destination.

Spans produced while it is disabled aren't delivered later. A destination that is already disabled keeps its reason.

type: "disabled"
beta_telemetry_destination_test_failure: object{ type: "failure", error }

The test span was not delivered.

type: "failure"
error: string

A message that describes why the test span was not delivered, including the HTTP status code when the destination returned one. Examples: HTTP error (status 403), timeout, TLS failure. It has the same form as the destination's delivery_health.last_error and never contains the destination's response body, any header value, a network address, or TLS details.

beta_telemetry_destination_test_response: object{ type: "telemetry_destination_test", result }

The result of one test span sent to a destination.

beta_telemetry_destination_test_result: BetaTelemetryDestinationTestSuccess or BetaTelemetryDestinationTestFailure

The outcome of a test: success, or failure with the reason.

beta_telemetry_destination_test_success: object{ type: "success" }

The destination answered the test span with a 2xx status.

type: "success"
beta_telemetry_destination_test_failure: object{ type: "failure", error }

The test span was not delivered.

type: "failure"
error: string

A message that describes why the test span was not delivered, including the HTTP status code when the destination returned one. Examples: HTTP error (status 403), timeout, TLS failure. It has the same form as the destination's delivery_health.last_error and never contains the destination's response body, any header value, a network address, or TLS details.

beta_telemetry_destination_test_success: object{ type: "success" }

The destination answered the test span with a 2xx status.

type: "success"
beta_telemetry_destination_traces: object{ content_mode, enabled, endpoint_url, max_content_bytes }

A telemetry destination's settings for the traces it receives.

content_mode: "metadata_only" or "content"

What the exported spans contain.

One of the following:
"metadata_only"

The spans contain identifiers, timing, status, token counts, and similar metadata. They don't contain prompt text, completion text, or tool inputs and outputs.

"content"

The spans contain the same metadata as metadata_only, plus message and tool content.

An organization with a data-handling restriction, such as under HIPAA, can't choose this mode. The API exports only metadata for such an organization, even to a destination that already has content.

enabled: boolean

Whether the destination receives traces. A destination whose enabled is false keeps its other settings.

endpoint_url: string

The full URL that the API posts traces to, exactly as registered, or null if the destination doesn't have one.

When it is null, the API posts traces to endpoint_url with /v1/traces appended.

max_content_bytes: number

The most bytes of content that one exported span can contain, or null if only the API's maximum applies.

Content means model prompts and responses, and tool inputs and outputs. The API shortens longer content to this size before it delivers the span. A destination whose content_mode is metadata_only keeps this value. It applies once content_mode is content.

formatint32
beta_telemetry_destination_traces_params: object{ content_mode, enabled, endpoint_url, max_content_bytes }

The settings for the traces that a telemetry destination receives, as a create or update request sets them. An omitted field takes its default on create and keeps its stored value on update.

content_mode: optional "metadata_only" or "content"

What the exported spans contain. Defaults to metadata_only on create.

On update, null sets metadata_only.

One of the following:
"metadata_only"

The spans contain identifiers, timing, status, token counts, and similar metadata. They don't contain prompt text, completion text, or tool inputs and outputs.

"content"

The spans contain the same metadata as metadata_only, plus message and tool content.

An organization with a data-handling restriction, such as under HIPAA, can't choose this mode. The API exports only metadata for such an organization, even to a destination that already has content.

enabled: optional boolean

Whether the destination receives traces. Defaults to true on create. It cannot be null.

endpoint_url: optional string

The full URL of your collector's traces endpoint, for a collector that takes traces on a path other than /v1/traces. The API posts traces to it exactly as given and appends nothing.

The same rules as for endpoint_url apply, except that any path is allowed. It must have the same scheme, host, and port as endpoint_url. At most 2,048 characters.

On create, null is the same as leaving it out. On update, null removes it. The API then posts traces to endpoint_url with /v1/traces appended. A change of this URL alone keeps the registered headers.

maxLength2048
max_content_bytes: optional number

The most bytes of content that one exported span can contain, from 1 up to the API's maximum. null sets no bound, so only the API's maximum applies.

On create, leaving it out is the same as null. The error for a value above the maximum states the maximum.

formatint32
beta_telemetry_destination_workspaces: BetaTelemetryDestinationWorkspacesAll or BetaTelemetryDestinationWorkspacesInclude or BetaTelemetryDestinationWorkspacesExclude

Which of the organization's workspaces a telemetry destination covers.

Several destinations can cover the same workspace. Each of them receives the workspace's spans while it is enabled.

The workspace list of an include or exclude destination isn't part of the destination object. List the destination's workspaces to read it. Add or remove one workspace at a time, or replace the whole list with an update. A list holds at most 1,000 workspaces.

beta_telemetry_destination_workspaces_all: object{ type: "all" }

The destination covers every workspace of the organization, including the default workspace, archived workspaces, and workspaces created later. It doesn't have a list.

type: "all"
beta_telemetry_destination_workspaces_all_params: object{ type: "all" }

Cover every workspace of the organization. Doesn't take workspace_ids.

An update that sets all empties the destination's workspace list.

type: "all"
beta_telemetry_destination_workspaces_exclude: object{ type: "exclude" }

The destination covers every workspace of the organization except the workspaces on its list. A workspace created later is covered until it is added to the list.

type: "exclude"
beta_telemetry_destination_workspaces_exclude_params: object{ type: "exclude", workspace_ids }

Cover every workspace of the organization except the workspaces on the list.

type: "exclude"
workspace_ids: optional array of string

The IDs of the workspaces on the destination's list (wrkspc_...). At most 100 per request.

On create, these workspaces become the destination's list. If you leave workspace_ids out, the list starts empty. If the API refuses one of the IDs, it doesn't create the destination.

On update, workspace_ids replaces the whole list. A workspace that stays on the list keeps its entry and its created_at. An empty array empties the list. If you leave workspace_ids out and the type stays the same, the list doesn't change. If you leave it out and the type changes, the new list starts empty. After a change to include without workspace_ids, the destination doesn't cover any workspace until one is added. After a change to exclude without workspace_ids, it covers every workspace.

An ID sent more than once is added once. An archived workspace can't be added to a list. An update can keep an archived workspace that is already on the list.

beta_telemetry_destination_workspaces_include: object{ type: "include" }

The destination covers the workspaces on its list, and no others.

type: "include"
beta_telemetry_destination_workspaces_include_params: object{ type: "include", workspace_ids }

Cover only the workspaces on the list.

type: "include"
workspace_ids: optional array of string

The IDs of the workspaces on the destination's list (wrkspc_...). At most 100 per request.

On create, these workspaces become the destination's list. If you leave workspace_ids out, the list starts empty. If the API refuses one of the IDs, it doesn't create the destination.

On update, workspace_ids replaces the whole list. A workspace that stays on the list keeps its entry and its created_at. An empty array empties the list. If you leave workspace_ids out and the type stays the same, the list doesn't change. If you leave it out and the type changes, the new list starts empty. After a change to include without workspace_ids, the destination doesn't cover any workspace until one is added. After a change to exclude without workspace_ids, it covers every workspace.

An ID sent more than once is added once. An archived workspace can't be added to a list. An update can keep an archived workspace that is already on the list.

beta_telemetry_destination_workspaces_params: BetaTelemetryDestinationWorkspacesAllParams or BetaTelemetryDestinationWorkspacesIncludeParams or BetaTelemetryDestinationWorkspacesExcludeParams

Which of the organization's workspaces a telemetry destination covers, as a create or update request sets it.

Назначения телеметрииРабочие пространства

Список рабочих пространств назначения телеметрии
$ ant beta:organization:telemetry-destinations:workspaces list
GET/v1/organizations/telemetry_destinations/{destination_id}/workspaces

Получить рабочие пространства из списка рабочих пространств назначения, начиная с самой новой записи.

Добавление рабочего пространства назначения телеметрии
$ ant beta:organization:telemetry-destinations:workspaces add
POST/v1/organizations/telemetry_destinations/{destination_id}/workspaces/{workspace_id}

Добавить одно рабочее пространство в список рабочих пространств назначения.

Удаление рабочего пространства назначения телеметрии
$ ant beta:organization:telemetry-destinations:workspaces remove
DELETE/v1/organizations/telemetry_destinations/{destination_id}/workspaces/{workspace_id}

Удалить одно рабочее пространство из списка рабочих пространств назначения.