OpenTelemetry eBPF Instrumentation
OpenTelemetry eBPF Instrumentation (OBI) is a lightweight eBPF-based agent that automatically generates OpenTelemetry traces and metrics for applications…
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
56/100 Fair
- Maintained
- 100last commit 15 days ago
- Popular
- 56622 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
- Security check
- 011 serious findings, 12 minor, CI, tests, OpenSSF Scorecard 7.1/10
Based on 4 of 5 factors.
Security check: 8 serious findings
- Uses github.com/gofiber/fiber/v2 v2.52.0, which has a known critical vulnerability (Go)
- Uses github.com/gofiber/fiber/v2 v2.52.0, which has a known critical vulnerability (Go)
- Uses github.com/gofiber/fiber/v2 v2.52.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.11.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.11.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.11.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.11.0, which has a known critical vulnerability (Go)
- Uses golang.org/x/crypto v0.11.0, which has a known critical vulnerability (Go)
Automated checks on commit 9e76b1a, 30 Oct 2026. Not an audit.
Availability: platform listings confirmed today
- GitHub stars
- 622
- Open issues
- 307
- Last commit
- 2026-11-06
- Latest release
- v1.0.0
- License
- Apache-2.0
- Activity
- steady
Checked 15 days ago - source: GitHub (open-telemetry/opentelemetry-ebpf-instrumentation)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Install the Python package first Run pip install opentelemetry-instrumentation-openai-v2 so your code can import the OpenAI tracking helpers. Without this, any code that tries to use OpenAIInstrumentor will fail. source
- Turn on tracking in your app Call OpenAIInstrumentor().instrument() before making OpenAI chat or embedding calls. If you skip this, your app will still work, but OpenAI calls won't produce the expected telemetry. source
- Add the upload extra only if needed Install opentelemetry-util-genai[upload] if you want to upload prompts and completions, because it pulls in fsspec (a file-system helper library). If you don't need that upload feature, you can skip it. source
- Pin to a release tag, not 'latest' OBI is still in development (v0.x) and can break between minor releases. Pin your Helm deployment to a specific semver release tag instead of 'latest', and review the release notes before upgrading. source
Fetched 41 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
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.
Answers sourced from github.com, github.com, opentelemetry.io, opentelemetry.io, platformengineeringplaybook.com
Community
Collected 48 days ago - public community threads