Skip to main content

​
Integration command

OpenClaw Gateway can export diagnostics through the diagnostics-otel plugin. Beacon can print a local OTLP/HTTP Gateway configuration and validate whether OpenClaw-derived events are arriving in the endpoint runtime log.
This is the gateway half of OpenClaw support, not the whole of it. These commands cover OpenClaw’s own OpenTelemetry export, which carries gateway traces and metrics — and, unless captureContent is explicitly enabled, no prompt, tool, or file content at all.What the agent did is collected by a separate, Beacon-managed plugin:
Both paths report under the same openclaw_gateway harness and are wanted together. See OpenClaw Gateway for the plugin, the config key token usage needs, and what is deliberately not collected.
Command syntax

​
Commands

print-config

Print OpenClaw Gateway OTLP setup guidance.

status

Show OpenClaw Gateway endpoint integration status.

validate

Validate whether OpenClaw OTLP-derived events are arriving.

​
Gateway setup

Start Beacon’s local endpoint collector:
Start Beacon's local endpoint collector
Install and enable the OpenClaw diagnostics plugin:
Install and enable the OpenClaw diagnostics plugin
Print the Gateway config values that point OpenClaw at Beacon’s local OTLP HTTP receiver:
Print the Gateway config values that point OpenClaw at Beacon's local OTLP HTTP receiver
By default, Beacon prints an endpoint of http://127.0.0.1:4318, protocol http/protobuf, and service name openclaw-gateway.
OpenClaw does not export raw prompt, response, tool, or system-prompt content unless diagnostics.otel.captureContent.* is explicitly enabled in the Gateway config. Beacon validation confirms at least one OpenClaw OTLP-derived event reached the runtime log; it does not prove logs, traces, and metrics are each flowing.

​
Flags

​
beacon endpoint integrations openclaw print-config

beacon endpoint integrations openclaw print-config prints OpenClaw Gateway OTLP setup guidance.
Print the configuration

​
Examples

Print guidance using the local OTLP HTTP receiver from the Beacon config:
Print guidance using the local OTLP HTTP receiver from the Beacon config
Print guidance for a custom local collector endpoint:
Print guidance for a custom local collector endpoint

​
beacon endpoint integrations openclaw status

beacon endpoint integrations openclaw status reports whether OpenClaw OTLP-derived events have been observed in the endpoint runtime log.
Check status

​
Examples

Show status:
Show status
Print status as JSON:
Print status as JSON
Check a custom runtime log:
Check a custom runtime log

​
beacon endpoint integrations openclaw validate

beacon endpoint integrations openclaw validate checks whether OpenClaw OTLP-derived events have arrived in the endpoint runtime log.
Run the validation check
If validation fails, Beacon prints OpenClaw setup guidance using any endpoint you provide.

​
Examples

Require an OpenClaw event in the last 10 minutes:
Require an OpenClaw event in the last 10 minutes
Validate and include custom setup guidance if no event is found:
Validate and include custom setup guidance if no event is found
Validate a custom runtime log:
Validate a custom runtime log

Agent harness integration model

See how Beacon discovers and configures supported runtime surfaces.

Supported runtimes

Compare agent harness support across local OTLP, hooks, and admin-configured integrations.

Endpoint agent

Install, repair, inspect, and uninstall the local endpoint agent.

Claude Cowork

Manage Claude Cowork OTLP export.