# OpenTelemetry eBPF Instrumentation

OpenTelemetry eBPF Instrumentation is a lightweight eBPF-based agent that automatically generates OpenTelemetry traces and metrics for applications running on Kubernetes, with no code changes required. It is open source and self-hosted, installable on Kubernetes (Helm).

Canonical page: https://ourlocalhost.com/app/4901/opentelemetry-ebpf-instrumentation

## Description

OpenTelemetry eBPF Instrumentation (OBI) is a lightweight eBPF-based agent that automatically generates OpenTelemetry traces and metrics for applications running on Kubernetes, with no code changes required. It is distributed as a Helm chart, letting operators add observability to workloads without embedding instrumentation SDKs in every container.

## Platform availability

Available on 1 of 10 platforms: Helm.

## Health score

56/100 (Fair), based on 4 of 5 factors.
- Maintained: 100 (last commit 15 days ago)
- Popular: 56 (622 GitHub stars)
- Easy to install: 25 (1 install platform, install notes)
- Security check: 0 (11 serious findings, 12 minor, CI, tests, OpenSSF Scorecard 7.1/10)

## Security check

8 serious findings: Uses github.com/gofiber/fiber/v2 v2.52.0, which has a known critical vulnerability; Uses github.com/gofiber/fiber/v2 v2.52.0, which has a known critical vulnerability; Uses github.com/gofiber/fiber/v2 v2.52.0, which has a known critical vulnerability; Uses golang.org/x/crypto v0.11.0, which has a known critical vulnerability; Uses golang.org/x/crypto v0.11.0, which has a known critical vulnerability; Uses golang.org/x/crypto v0.11.0, which has a known critical vulnerability; Uses golang.org/x/crypto v0.11.0, which has a known critical vulnerability; Uses golang.org/x/crypto v0.11.0, which has a known critical vulnerability.
Automated checks on commit 9e76b1a, 30 Oct 2026. Not an audit.

## Links

- GitHub: https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation
- Kubernetes (Helm): https://artifacthub.io/packages/helm/opentelemetry-helm/opentelemetry-ebpf-instrumentation

## Common questions

### How can I get more diagnostic detail when OBI misbehaves?

OBI provides troubleshooting tools and configuration options for diagnosing issues. You can increase logging verbosity by setting the log_level configuration.

### What production deployment guidance is highlighted for OBI?

The production guide covers Kubernetes setup, an SDK-versus-eBPF decision framework, and limitations to know. It highlights deploying zero-code observability with under 2% CPU overhead.

### Why are Go and Rust mentioned when discussing tracing setup?

The docs note that in some compiled languages like Go or Rust, you must manually add tracepoints to the code. OBI is the eBPF instrumentation option described alongside that need.

### Where can users ask code-related questions about the project?

GitHub Discussions is the forum for discussing code, asking questions, and collaborating with the developer community.

### What mechanism does the repository say OBI uses for user-space applications?

It provides eBPF instrumentation based on the OpenTelemetry standard.

---
Source: Our Local Host (https://ourlocalhost.com/app/4901/opentelemetry-ebpf-instrumentation), the self-hosted and open-source app directory.
