Backends¶
The plugin exports telemetry via standard OTLP (OpenTelemetry Protocol), which means it works with any OpenTelemetry-compatible backend.
Supported Backends¶
| Backend | Direct Export | Via Collector | Guide |
|---|---|---|---|
| Dynatrace | ✅ | ✅ | Setup → |
| Grafana (Tempo + Mimir) | ✅ | ✅ | Setup → |
| Datadog | ❌ | ✅ | Generic → |
| Honeycomb | ✅ | ✅ | Generic → |
| New Relic | ✅ | ✅ | Generic → |
| Splunk | ❌ | ✅ | Generic → |
| Jaeger | ✅ | ✅ | Generic → |
| SigNoz | ✅ | ✅ | Generic → |
| OTel Collector | — | — | Setup → |
Direct Export vs. Collector¶
Direct Export¶
flowchart LR
A[OpenClaw Plugin] -->|OTLP| B[Backend]- Simpler setup — no extra components
- Works well for single-backend setups
- Backend credentials are in the OpenClaw config
Via OTel Collector (Recommended)¶
flowchart LR
A[OpenClaw Plugin] -->|OTLP| B[OTel Collector]
B -->|OTLP| C[Dynatrace]
B -->|OTLP| D[Grafana]
B -->|Prometheus| E[Prometheus]- Batching & retry — handles network hiccups gracefully
- Processing — filter, transform, and enrich data before export
- Fan-out — send to multiple backends simultaneously
- Decoupled auth — backend credentials stay on the collector, not in OpenClaw
- Sampling — reduce data volume for high-traffic agents
Recommendation
Use the OTel Collector in production. Use direct export for quick development testing.