Export platform telemetry
Decide whether the platform sends its own logs, metrics and traces to an external OpenTelemetry backend, and to which one.
Requires: kernel/telemetrySettings/manage
The platform can send its own errors, logs, metrics and traces — not your workloads' — to an OpenTelemetry backend outside the cluster. Export is off by default: nothing leaves the cluster until a platform administrator turns it on, and turning it on is the point at which some of the platform's data leaves your perimeter.
Changing it needs kernel/telemetrySettings/manage at the platform root, which Platform Owner and
Platform Contributor hold.
Turn export on
Open Settings → Platform Settings and the Telemetry tab.
| Field | What to enter |
|---|---|
| Export platform telemetry | The master switch. Off, the collector inside the cluster keeps running but sends nothing out |
| OTLP/HTTP endpoint | Your backend's base URL, for example https://observe.example.com/api/my-org. It must use https://. Do not add /v1/logs — the exporter appends the signal's path itself |
| Credential | Either a complete Authorization header value starting with Basic — OpenObserve issues one under IAM → Ingestion Tokens — or a bare token to combine with Username |
| Username | Combined with a bare token into a Basic header. Not used when the credential is already a complete header |
| Minimum log level exported | Log records below this level are dropped before they leave the cluster. The default, Warning, exports warnings, errors and critical errors. Metrics and traces are not filtered |
Choose Save.
The credential is always sent as a Basic header, and is stored encrypted and never shown again. Leave it blank when you change other fields to keep the stored one; it cannot be cleared.
Traces are exported in full: the tab has no sampling setting, and saving from it sets sampling to every trace.
What saving does
Saving rewrites the configuration of the platform's telemetry collector, which restarts to pick it up. No platform module restarts, so changing the destination or the level during an incident is safe while the platform is under load.
If the installation has no telemetry collector yet, the settings are saved but the tab says they are not yet in effect; nothing is exported until the collector is deployed by the installer.
Settings from installation
Until the tab has been saved once, it shows These values come from the install-time configuration. Saving here takes ownership of them. — the values in the platform API's own configuration. Export set up in the installer is not among them: the tab then reads Off, and the first save replaces the installer's collector configuration with what the tab shows.