Browser Telemetry
Update OTLP destination by ID or name
Changed onUpdate 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 organization. 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. Requires an organization-scoped credential or dashboard authentication; project-scoped credentials receive a 403.
patch/telemetry/destinations/{id_or_name}
Request
- Base URLhttps://api.onkernel.com
- URLhttps://api.onkernel.com/telemetry/destinations/{id_or_name}
- AuthHTTP bearer
Path parameters
id_or_namestring required
OTLP destination ID or name
Request body
Response
OTLP destination updated
Changes
- info
endpoint added
- info