Sign in
latestOpenAPI 3.1.02026-08-22154287463.4 KB

858365328f92

Browser Telemetry

Create an OTLP destination

Create an OTLP export destination in the resolved project. Names must be unique within the project.

post/telemetry/destinations

Request body

descriptionstring
endpointstring required

Base endpoint of the OTLP/HTTP collector, without a signal path. Kernel appends the signal path itself, so pass https://api.honeycomb.io rather than https://api.honeycomb.io/v1/logs. If your provider's docs give you a signal-specific URL, drop the trailing /v1/logs, /v1/traces, or /v1/metrics — an endpoint that already carries one is rejected.

Must be http or https, must resolve to a public address, and must carry no query string or fragment. Examples: https://api.honeycomb.io, https://otlp-gateway-prod-us-east-0.grafana.net/otlp, https://otlp.datadoghq.com (Datadog's OTLP intake for US1, not its logs intake).

headersobject

Headers sent with each export request, typically an ingestion key. Encrypted at rest and returned redacted. Names and values must be valid HTTP header tokens, and the names and values together cannot exceed 8192 bytes. Names are matched case-insensitively and stored canonicalized, so supplying two spellings of one header is rejected.

namestring required

Unique within the project.

Response

OTLP destination created

created_atstring date-time required
descriptionstring
endpointstring required

OTLP/HTTP endpoint telemetry is sent to.

headersobject required

Headers sent with each export request. Names are returned in canonical form (Authorization, not authorization). Values are returned redacted as empty strings, so the keys are visible but the credentials are not.

idstring required
namestring required

Unique within the project. Usable in place of the ID when selecting a destination, so it cannot be shaped like an ID.

updated_atstring date-time required