OpenClaw Gateway Telemetry in Beacon | Asymptote
What is OpenClaw Gateway?
OpenClaw Gateway support documents the Gateway diagnostics export path and gives teams CLI helpers for configuring and validating telemetry.
Collection path: Gateway-configured OTLP/HTTP
Authoritative date: May 20, 2026 from v0.0.17 in the Beacon CLI changelog.
How Beacon reads OpenClaw Gateway
OpenClaw Gateway exports diagnostics over OTLP or HTTP. Beacon prints local settings, checks status, validates observed events, and filters noisy operational metrics by default.
The result is normalized into Beacon's endpoint event schema so security teams can investigate activity by harness, repository, session, user, model, command, file, tool, MCP server, or approval context where the runtime exposes those fields.
Telemetry coverage
- OTLP logs, traces, and metrics from the Gateway diagnostics plugin
- Configuration printing through Beacon CLI integration commands
- Status checks and validation events
- Runtime log output through the local collector
What you can do now
- Point OpenClaw Gateway diagnostics at Beacon.
- Validate Gateway telemetry without changing unrelated runtime settings.
- Keep low-level operational metrics out of endpoint JSONL unless needed.
Get started
- Run beacon endpoint integrations openclaw to print local Gateway settings.
- Apply those settings in OpenClaw Gateway.
- Use Beacon validation commands to confirm events arrive.