Deploy Beyla as a DaemonSet or sidecar with the target process PID or service name configured in the discovery section
Set the OTEL exporter endpoint so Beyla forwards spans and metrics to your OTel Collector or Grafana Cloud endpoint
Configure the open-port or executable-name selectors to scope which processes Beyla attaches to
Verify kernel version meets the minimum BPF CO-RE requirement and that BTF is available on the host
Check Beyla's internal metrics endpoint to confirm it is generating spans before integrating with dashboards
Known gotchas
Beyla requires a Linux kernel that supports CO-RE (BTF-enabled); many cloud node images need explicit verification before assuming support
Running Beyla in a container requires elevated privileges or specific Linux capabilities; dropping capabilities too aggressively breaks eBPF map access
Beyla instruments at the network boundary so it captures HTTP/gRPC but not intra-process calls or non-network spans
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp