Configure log export destination
Configures the external OTLP endpoint a function’s runtime and/or invocation logs are pushed to as they happen. This operation is a full replace, not a patch: endpoint, headers, runtime_export_enabled, and invocation_export_enabled are all required on every call — omitting any of them is a 422, not “keep the current value”. Headers are encrypted at rest and never returned in any response.
The endpoint must be an HTTPS URL. When export is configured, new log records are converted to OTLP log records and delivered continuously; export never bypasses platform log storage, and delivery retries with a bounded policy while the destination is unreachable. Only logs generated after configuration are exported — there is no historical replay.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Function ID
Body
Full-replace configuration body. All fields are required on every call: the API treats PUT as a replace (RFC 7231), so omitting any field is a 422, not "keep the current value".
HTTPS URL to push logs to
Headers attached to every export push, as key-value pairs (e.g. an auth token the collector expects). Required even when empty — {} means "no headers". Encrypted at rest; never returned.
Export runtime logs (function stdout/stderr) to this destination
Export invocation records (one per HTTP request) to this destination
Response
Log export configuration replaced successfully
Metadata-only view of a function's log export destination. Header values are write-only (encrypted server-side) and never appear in any response.