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.

​
OpenClaw Gateway

Beacon supports OpenClaw Gateway through gateway-configured OTLP/HTTP export.

​
Prerequisites

Before enabling OpenClaw Gateway telemetry, make sure:
  • You can configure the OpenClaw Gateway diagnostics-otel plugin.
  • beacon endpoint install has run so the local collector and runtime log path exist.
  • You have run beacon endpoint integrations openclaw print-config to get the local OTLP/HTTP settings for Gateway.
  • OpenClaw Gateway points at the same Beacon collector and runtime log that you will inspect with Beacon commands.
  • captureContent is explicitly enabled in OpenClaw if you expect prompt content rather than metadata-only telemetry.

​
Collection path

OpenClaw Gateway emits OTLP logs, traces, and metrics through the diagnostics-otel plugin. Beacon prints local OTLP/HTTP Gateway config and validates whether OpenClaw-derived events have reached the endpoint runtime log.

​
Discovery and status

Beacon validates OpenClaw Gateway support by scanning the endpoint runtime log for OpenClaw-derived events after Gateway diagnostics are configured. Use beacon endpoint integrations openclaw status to check whether OpenClaw events have been observed.

​
Install or configuration support

OpenClaw Gateway is configured in OpenClaw, not by beacon endpoint install. Use beacon endpoint integrations openclaw print-config to print local Gateway OTLP settings, then configure OpenClaw Gateway with the diagnostics-otel plugin. OpenClaw Gateway is not hook-based.

​
Telemetry coverage

AreaSupport
Prompt telemetryDisabled by default unless OpenClaw captureContent settings are explicitly enabled
Command, tool, and file telemetrySupported for OTLP logs, traces, and metrics emitted by the Gateway diagnostics plugin
Local JSONL and dashboardSupported after events reach the collector
MDM deploymentSupported for the endpoint agent; Gateway diagnostics configuration is managed in OpenClaw

​
Deployment notes

Because OpenClaw Gateway configuration lives in OpenClaw, use Beacon’s OpenClaw integration commands to print the expected local OTLP/HTTP configuration and validate observed runtime events. If no OpenClaw events appear, confirm the Gateway diagnostics plugin is enabled, the OTLP endpoint points at the Beacon collector, and the runtime log being inspected is the same log the collector writes.

Supported agent harnesses

Return to the runtime support overview.

OpenClaw commands

Print config, check status, and validate OpenClaw telemetry.