Browser Telemetry

Create an OTLP destination

Changed on

Create an OTLP export destination in the authenticated organization. Names must be unique within the organization. Requires an organization-scoped credential or dashboard authentication; project-scoped credentials receive a 403.

post/telemetry/destinations

Request

  • Base URL
    https://api.onkernel.com
  • URL
    https://api.onkernel.com/telemetry/destinations
  • Auth
    HTTP bearer

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 organization.

Response

OTLP destination created

consecutive_failuresinteger required

Failed deliveries since the last success, as observed by the relay process that wrote the latest outcome. Zero means the most recently recorded outcome succeeded.

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). Non-dashboard reads return values redacted as empty strings, so the keys are visible but the credentials are not. Dashboard reads return the stored values.

idstring required
last_errorstring

Sanitized class of the delivery failure recorded at last_error_at. It is retained after a later success, so its presence does not mean the destination is currently failing. Response bodies, endpoint URLs, credentials, and raw transport errors are never returned.

last_error_atstring date-time

Timestamp of the most recent failed delivery. It is retained after a later success, so it can predate last_export_at. Read consecutive_failures to tell whether the destination is currently failing.

last_export_atstring date-time

Timestamp of the most recent successful delivery. Moves only on success.

namestring required

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

updated_atstring date-time required

Changes