Telemetry Collection
Configure the local Beacon endpoint agent so supported agent harnesses can export telemetry to the local OpenTelemetry Collector and Beacon runtime log.Configure endpoint telemetry
For a non-root local setup, run the default install:127.0.0.1. Gemini CLI telemetry is opt-in; include gemini in the endpoint harness list when you want Beacon to manage local Gemini OTLP settings. Beacon also discovers Gemini CLI, GitHub Copilot CLI, Grok Build, Hermes Agent, OpenCode, and Factory Droid, can validate Copilot and Droid launch-environment telemetry when you manage those settings through MDM or another customer-owned policy, and can validate OpenClaw Gateway events after you configure Gateway OTLP/HTTP export.
Production endpoint install is currently supported on macOS. The default mode uses per-user paths; use
--system as root for package or MDM deployments.Content Handling
Beacon can record supported prompt, tool, command, file, approval, policy, and runtime context when the source runtime emits it. Before events are written toruntime.jsonl or sent through configured destinations, Beacon applies redaction, sanitization, truncation, and event-size limits.
Beacon filters generic process/runtime OTLP metrics, Copilot CLI and OpenClaw operational metrics, and high-volume Codex spans out of the local JSONL log by default. Use --include-runtime-metrics for low-level metrics, or --include-codex-spans only when you need raw Codex spans for troubleshooting.
Related
Paths
Review files, logs, collector config, ports, and hook locations.
Endpoint agent
Review the endpoint install, status, repair, and uninstall commands.