OpenTelemetry eBPF Kernel Collector

OpenTelemetry eBPF Kernel Collector is an OpenTelemetry component that uses eBPF to collect low-level Linux kernel and network telemetry for observability…

  • Network Services
  • Tools & Utilities
OpenTelemetry eBPF Kernel Collector is an OpenTelemetry component that uses eBPF to collect low-level Linux kernel and network telemetry for observability without instrumenting application code.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • 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.

40/100 Fair

Maintained
51last commit 221 days ago
Popular
52408 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
201 serious finding, 2 minor, CI, tests, OpenSSF Scorecard 6.1/10

Based on 4 of 5 factors.

GitHub stars
408
Open issues
47
Last commit
2026-04-13
Latest release
v0.11.0
License
Apache-2.0
Activity
stale

Checked yesterday - source: GitHub (open-telemetry/opentelemetry-network)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Point OBI to your tracing backend In your OBI config file, set `otel_traces_export.endpoint` to the address of the service that receives traces and set `open_port` to a port number shown in the example. The endpoint tells OBI where to send trace data, so if it is missing or wrong the collector can run but your traces will not arrive. source
  • Start the Docker example with Compose Docker Compose is a helper that starts several packaged programs, called containers, from one file. Run `docker compose -f compose-example.yml up` to start the OBI example and its test services; if this command is not run, the collector will not be running. source
  • Put the OBI command in PATH if not using Docker If you install the OBI binary directly, copy it to a PATH directory such as `/usr/local/bin` and verify it with `obi --version`. PATH is the list of folders your terminal checks for commands, so without this step `obi` may not be found from other folders. source

Fetched 53 days ago - each note links to its source

Alternatives (1)

  • dash0 - Full-Stack Infrastructure Monitoring without Limits.

Checked 40 days ago - source: AlternativeTo

Common questions

Does the kernel collector need special Docker permissions?

Yes. It needs privileged access because it uses eBPF, so pass --privileged, --pid host, and --network host to Docker.

Why might the collector run but no traces arrive?

The tracing backend address can be missing or wrong. Set otel_traces_export.endpoint to the service that receives traces, and set open_port to the example port.

What should I do if the obi command is not found after a direct binary install?

Copy the binary to a PATH directory such as /usr/local/bin and verify it with obi --version.

What should I check when the kernel collector has configuration or permission problems?

Check the specific system configurations and permissions it requires, and use the troubleshooting guidance for diagnosing common issues.

Answers sourced from deepwiki.com, github.com, opentelemetry.io, opentelemetry.io

Community

No community discussions collected yet.