Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

OpenTelemetry eBPF Profiler

github.com

  • Free plan
  • Linux
  • Self-hosted
6.9 Club score Visit github.com

What OpenTelemetry eBPF Profiler is

OpenTelemetry eBPF Profiler is a free, open-source profiler for whole Linux systems. Using eBPF, it collects cross-language profiles with stack traces spanning kernel code, system libraries, and high-level runtimes, including native inline frames. Supported languages include C/C++, Rust, Zig, Go, HotSpot JVM, Python, Ruby, PHP, Node.js, V8, Perl, Erlang, and .NET. Profiling does not require loading agents into application processes, adding instrumentation, changing runtime settings, or restarting interpreters and virtual machines. The project reports tested upper limits of 1% CPU and 250 MB of memory, with typical use below those ceilings. The supported deployment path is an OpenTelemetry Collector receiver. Pyroscope is named as a database that can ingest the profiling data, while mature production-ready backends have yet to emerge. The implementation of the Alpha OpenTelemetry Profiles signal is functional but evolving. Builds target amd64 and arm64; newer commits may require Linux kernel 5.10 or later.

Who it suits

It suits Linux operators and developers needing system-wide profiling across native and managed runtimes. OpenTelemetry Collector users have the stated supported deployment path.

Good to know, and what to watch

  • Profiles many native and high-level languages
  • No in-process agents or restarts required
  • Reports low tested resource ceilings
  • Supports amd64 and arm64 builds
  • Integrates with OpenTelemetry Collector
  • Linux-only deployment
  • Recent commits may require kernel 5.10
  • Profiles signal implementation is still evolving
  • Mature production backends have yet to emerge

The verdict

This profiler offers non-intrusive, cross-language Linux visibility with modest stated overhead. Its evolving signal and backend ecosystem warrant planning before production adoption.

What the maker publishes

Architecture
The project supports amd64 and arm64 builds, and says macOS and Windows users need a Linux VM to build and run the agent. source
Architecture support
The project supports ARM64 unwinders and says its provided build targets support amd64 and arm64. source
Backend integration
The README names Pyroscope as an open-source database that natively supports ingesting OpenTelemetry profiling data. source
Backends
The README names Pyroscope as an open-source database that natively supports ingesting OpenTelemetry profiling data, and says mature production-ready backends have yet to emerge. source
Collector integration
The project says its profiler is integrated into the OpenTelemetry Collector as a receiver and identifies that configuration as the supported path going forward. source
Community and support
The project invites bug reports, feature requests, documentation improvements, and code contributions, and directs discussion to the #otel-profiles channel on CNCF Slack. source
Development backend limitation
The README says devfiler is for testing, experimentation and development, and should not be used as a production backend. source
Development binaries
The standalone agent and local Collector receiver binaries are described as unsupported, subject to removal, and unsuitable for production deployment. source
Languages
It supports native code including C/C++, Rust, Zig and Go, as well as Hotspot JVM, Python, Ruby, PHP, Node.js, V8, Perl, Erlang and .NET. source
License
The project is licensed under Apache License 2.0, and its eBPF source code is licensed under GPL 2.0. source
Linux requirement
The profiler is Linux-only; recent commits may require Linux kernel 5.10 or later, while earlier commits supported 5.4 or 4.19. source
Low overhead
The project says its tested upper limits are 1% CPU and 250 MB of memory, and that the agent typically stays well below those limits. source
No in-process agent
Profiling does not require loading agents or libraries into the processes being profiled. source
Non-intrusive profiling
The profiler does not need to load agents or libraries into profiled processes or require interpreter and VM reconfiguration, instrumentation, or restarts. source
No runtime changes
The agent supports unwinding supported languages in their default configuration without reconfiguration, instrumentation or interpreter or VM restarts. source
OpenTelemetry integration
The profiler is integrated into the OpenTelemetry Collector as a receiver, which the project identifies as the supported configuration going forward. source
Profile format
It implements the Alpha OpenTelemetry Profiles signal. source
Profiling signal status
The agent has a functional but work-in-progress, evolving implementation of the recently released Alpha OpenTelemetry Profiles signal. source
Purpose
It is a whole-system, cross-language profiler for Linux that uses eBPF. source
Security reporting
The security policy asks reporters not to use public GitHub issues and recommends the repository’s private vulnerability reporting channel. source
Stack traces
It supports mixed stack traces from kernel space through system libraries into high-level languages, and native inline frames. source
Standalone binary limitation
The standalone profiling agent and local profiling-receiver binaries are described as unsupported, potentially removable, and unsuitable for production deployment. source
Support and community
The project says it is developed by the OpenTelemetry Profiling SIG and directs questions and discussion to the #otel-profiles channel on CNCF Slack. source
System requirements
The profiler is Linux-only; later commits may require Linux kernel 5.10 or newer, while earlier commits supported kernels down to 5.4 or 4.19. source

Checked against the maker's pages on 4 Oct 2026.