Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.asymptotelabs.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
beacon endpoint integrations openclaw

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. 
beacon endpoint integrations openclaw [command]

​
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: 
beacon endpoint install
Install and enable the OpenClaw diagnostics plugin: 
openclaw plugins install clawhub:@openclaw/diagnostics-otel
openclaw plugins enable diagnostics-otel
Print the Gateway config values that point OpenClaw at Beacon’s local OTLP HTTP receiver: 
beacon endpoint integrations openclaw print-config
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

FlagDescription
--endpoint <url>OTLP HTTP endpoint to show in setup guidance. Defaults to Beacon’s configured local OTLP HTTP receiver
--since <duration>Require an OpenClaw event within this duration, such as 10m. Validate only
--jsonPrint status as JSON. Status only
--userUse per-user endpoint paths. Enabled by default
--systemUse system endpoint paths and launch daemon
--log-path <path>Runtime JSONL log path

​
beacon endpoint integrations openclaw print-config

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

​
Examples

Print guidance using the local OTLP HTTP receiver from the Beacon config: 
beacon endpoint integrations openclaw print-config
Print guidance for a custom local collector endpoint: 
beacon endpoint integrations openclaw print-config \
  --endpoint http://127.0.0.1:14318

​
beacon endpoint integrations openclaw status

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

​
Examples

Show status: 
beacon endpoint integrations openclaw status
Print status as JSON: 
beacon endpoint integrations openclaw status --json
Check a custom runtime log: 
beacon endpoint integrations openclaw status \
  --log-path /path/to/runtime.jsonl

​
beacon endpoint integrations openclaw validate

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

​
Examples

Require an OpenClaw event in the last 10 minutes: 
beacon endpoint integrations openclaw validate --since 10m
Validate and include custom setup guidance if no event is found: 
beacon endpoint integrations openclaw validate \
  --since 10m \
  --endpoint http://127.0.0.1:14318
Validate a custom runtime log: 
beacon endpoint integrations openclaw validate \
  --log-path /path/to/runtime.jsonl

Runtime integrations

See how Beacon discovers and configures supported runtime surfaces.

Supported runtimes

Compare runtime 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.