Skip to main content
OpenClaw can expose diagnostics metrics through the official diagnostics-prometheus plugin. It listens to trusted diagnostics plus internally tagged, dispatcher-owned diagnostic events (queue, memory, and session-recovery signals), and renders a Prometheus text endpoint at:
Content type is text/plain; version=0.0.4; charset=utf-8, the standard Prometheus exposition format.
The route uses Gateway authentication (operator scope, trusted-operator surface). Do not expose it as a public unauthenticated /metrics endpoint. Scrape it through the same auth path you use for other operator APIs.
For traces, logs, OTLP push, and OpenTelemetry GenAI semantic attributes, see OpenTelemetry export.

Quick start

1

Install the plugin

2

Enable the plugin

3

Restart the Gateway

The HTTP route is registered at plugin startup, so reload after enabling.
4

Scrape the protected route

Send the same gateway auth your operator clients use:
5

Wire Prometheus

diagnostics.enabled defaults to true; set it to false only in tightly constrained environments. If it is false, the plugin still registers the HTTP route, but no diagnostic events flow into the exporter, so the response is empty.

Metrics exported

Label policy

Prometheus labels stay bounded and low-cardinality. The exporter does not emit raw diagnostic identifiers such as runId, sessionKey, sessionId, callId, toolCallId, message IDs, chat IDs, or provider request IDs.Label values are redacted and must match OpenClaw’s low-cardinality character policy. Values that fail the policy are replaced with unknown, other, or none, depending on the metric. Labels that look like scoped agent session keys are also replaced with unknown.
The exporter caps retained time series in memory at 2048 series across counters, gauges, and histograms combined. New series beyond that cap are dropped, and openclaw_prometheus_series_dropped_total increments by one each time.Watch this counter as a hard signal that an attribute upstream is leaking high-cardinality values. The exporter never lifts the cap automatically; if it climbs, fix the source rather than disabling the cap.
  • prompt text, response text, tool inputs, tool outputs, system prompts
  • Talk transcripts, audio payloads, call ids, room ids, handoff tokens, turn ids, and raw session ids
  • raw provider request IDs (only bounded hashes, where applicable, on spans — never on metrics)
  • session keys and session IDs
  • hostnames, file paths, secret values

PromQL recipes

Prefer gen_ai_client_token_usage for cross-provider dashboards: it follows the OpenTelemetry GenAI semantic conventions and is consistent with metrics from non-OpenClaw GenAI services.

Choosing between Prometheus and OpenTelemetry export

OpenClaw supports both surfaces independently. You can run either, both, or neither.
  • Pull model: Prometheus scrapes /api/diagnostics/prometheus.
  • No external collector required.
  • Authenticated through normal Gateway auth.
  • Surface is metrics only (no traces or logs).
  • Best for stacks already standardized on Prometheus + Grafana.

Troubleshooting

  • Check that diagnostics.enabled is not set to false in config (it defaults to true).
  • Confirm the plugin is enabled and loaded with openclaw plugins list --enabled.
  • Generate some traffic; counters and histograms only emit lines after at least one event.
The endpoint requires the Gateway operator scope (auth: "gateway" with gatewayRuntimeScopeSurface: "trusted-operator"). Use the same token or password Prometheus uses for any other Gateway operator route. There is no public unauthenticated mode.
A new attribute is exceeding the 2048-series cap. Inspect recent metrics for an unexpectedly high-cardinality label and fix it at the source. The exporter intentionally drops new series instead of silently rewriting labels.
The plugin keeps state in memory only. After a Gateway restart, counters reset to zero and gauges restart at their next reported value. Use PromQL rate() and increase() to handle resets cleanly.