Skip to main content
OpenClaw exports diagnostics through the official diagnostics-otel plugin using OTLP/HTTP (protobuf). Logs can also be written as stdout JSONL for container and sandbox log pipelines. Any collector or backend that accepts OTLP/HTTP works without code changes. For local file logs, see Logging.
  • Diagnostics events are structured, in-process records emitted by the Gateway and bundled plugins for model runs, message flow, sessions, queues, and exec.
  • diagnostics-otel subscribes to those events and exports them as OpenTelemetry metrics, traces, and logs over OTLP/HTTP, and can mirror log records to stdout JSONL.
  • Provider calls receive a W3C traceparent header from the actual current OpenTelemetry model-call span when the provider transport accepts custom headers. Diagnostic IDs remain local correlation keys, and plugin-emitted trace context is not propagated.
  • Exporters attach only when both the diagnostics surface and the plugin are enabled, so in-process cost stays near zero by default.
This page is an index. OpenTelemetry export is documented on five pages, one per reader job. Open the page that matches your task.

​
Where each section moved

Every section heading from the previous single-page version keeps its anchor here, so an existing link such as /gateway/opentelemetry#gateway-rpc still resolves. Each entry points at the page that now holds the content.