beyla

Auto-instrument HTTP and gRPC traffic in Kubernetes using eBPF to generate traces and metrics.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/1k-off/umbraco-observability-playground --skill beyla-1k-off
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beyla
Source: https://github.com/1k-off/umbraco-observability-playground/tree/main/.agents/skills/beyla
Command: npx skills add https://github.com/1k-off/umbraco-observability-playground --skill beyla-1k-off

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beyla eliminates the need to modify application code to gain meaningful observability, turning live HTTP and gRPC traffic into traces and metrics for debugging and performance analysis.

Core Features & Use Cases

  • Zero-code HTTP/gRPC instrumentation: Automatically generates traces and server/client duration metrics from in-cluster traffic.
  • Kubernetes-ready discovery: Targets services by port, process name, pod metadata, or K8s namespace/pod/deployment selectors to instrument without redeploying apps.
  • OTLP and Prometheus integration: Exports traces to Tempo (via OTLP) and metrics via Prometheus (or OTLP metrics) to plug into existing observability pipelines.
  • Production safety controls: Helps manage trace cardinality using route pattern matching and ignore strategies to prevent path explosion.
  • eBPF requirements and troubleshooting guidance: Provides concrete kernel, privilege, and deployment settings needed for reliable eBPF capture.

Quick Start

Deploy Beyla to your Kubernetes cluster and point it at your Tempo/Prometheus endpoints so it can auto-instrument traffic and start emitting traces and metrics.

Frequently Asked Questions about beyla

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get Prometheus metrics and traces without modifying application code?

You can get Prometheus metrics and traces without modifying application code by using Grafana Beyla to auto-instrument HTTP and gRPC traffic via eBPF. It automatically generates traces and duration metrics from live in-cluster traffic.

Does eBPF auto-instrumentation work with Kubernetes services?

Yes, eBPF auto-instrumentation works with Kubernetes services by targeting them through port, process name, pod metadata, or K8s namespace and deployment selectors. This allows cluster-wide instrumentation without redeploying applications.

How do I export eBPF traces and metrics to Tempo and Prometheus?

To export eBPF traces and metrics to Tempo and Prometheus, you must configure Beyla for OTLP trace export and Prometheus or OTLP metrics export. This plugs the auto-generated signals directly into your existing observability pipelines.

What Kubernetes privileges and kernel requirements are needed for eBPF observability?

eBPF observability requires kernel BTF support and elevated privileges, specifically host PID namespace access or appropriate capabilities. These Kubernetes deployment settings are necessary for reliable eBPF capture and process discovery.

How do I prevent trace cardinality explosion when auto-instrumenting HTTP traffic?

You prevent trace cardinality explosion when auto-instrumenting HTTP traffic by using Beyla's production safety controls. These manage trace cardinality through route pattern matching and ignore strategies to prevent path explosion.

What is the best way to instrument cluster-wide HTTP and gRPC traffic for observability?

The best way to instrument cluster-wide HTTP and gRPC traffic for observability is deploying Beyla to your Kubernetes cluster. Point it at your Tempo and Prometheus endpoints so it can auto-instrument traffic and start emitting traces and metrics immediately.