- Home
- Continuous Profiling Tools
- OpenTelemetry eBPF Profiler
On the recordRead 4 Oct 202624 facts
OpenTelemetry eBPF Profiler
On the record
- Architecture
- The project supports amd64 and arm64 builds, and says macOS and Windows users need a Linux VM to build and run the agent.github.com · read 4 Oct 2026
- Architecture support
- The project supports ARM64 unwinders and says its provided build targets support amd64 and arm64.github.com · read 4 Oct 2026
- Backend integration
- The README names Pyroscope as an open-source database that natively supports ingesting OpenTelemetry profiling data.github.com · read 4 Oct 2026
- 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.github.com · read 4 Oct 2026
- 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.github.com · read 4 Oct 2026
- 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.github.com · read 4 Oct 2026
- Development backend limitation
- The README says devfiler is for testing, experimentation and development, and should not be used as a production backend.github.com · read 4 Oct 2026
- Development binaries
- The standalone agent and local Collector receiver binaries are described as unsupported, subject to removal, and unsuitable for production deployment.github.com · read 4 Oct 2026
- 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.github.com · read 4 Oct 2026
- License
- The project is licensed under Apache License 2.0, and its eBPF source code is licensed under GPL 2.0.github.com · read 4 Oct 2026
- 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.github.com · read 4 Oct 2026
- 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.github.com · read 4 Oct 2026
- No in-process agent
- Profiling does not require loading agents or libraries into the processes being profiled.github.com · read 4 Oct 2026
- 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.github.com · read 4 Oct 2026
- No runtime changes
- The agent supports unwinding supported languages in their default configuration without reconfiguration, instrumentation or interpreter or VM restarts.github.com · read 4 Oct 2026
- OpenTelemetry integration
- The profiler is integrated into the OpenTelemetry Collector as a receiver, which the project identifies as the supported configuration going forward.github.com · read 4 Oct 2026
- Profile format
- It implements the Alpha OpenTelemetry Profiles signal.github.com · read 4 Oct 2026
- Profiling signal status
- The agent has a functional but work-in-progress, evolving implementation of the recently released Alpha OpenTelemetry Profiles signal.github.com · read 4 Oct 2026
