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.
Path parameters
Function ID
Request body
Response
Log export configuration replaced successfully