Sign in
latestOpenAPI 3.1.02026-08-22154287463.4 KB

858365328f92

Browser Telemetry

Update OTLP destination by ID or name

Update an OTLP destination. Sessions already exporting to it pick up the new values without restarting, which makes this the way to rotate credentials without interrupting export.

Names must be unique within the project. Renaming is refused with a 409 while a managed auth connection selects this destination by name, since that connection resolves the name on every login. Every other field, including headers, stays editable.

patch/telemetry/destinations/{id_or_name}

Path parameters

id_or_namestring required

OTLP destination ID or name

Request body

descriptionstring
endpointstring

Base endpoint of the OTLP/HTTP collector, without a signal path. Same rules as on create.

headersobject

Edits stored headers key by key rather than replacing the map. A string value adds or replaces that header, null deletes it, and any key you omit is left as it is. Names are matched case-insensitively, so authorization replaces a stored Authorization rather than adding a second entry. This is the credential rotation path; sessions already exporting pick up the new values without restarting. Names and values must be valid HTTP header tokens, and the names and values together cannot exceed 8192 bytes.

namestring

Response

OTLP destination updated

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