opentelemetry-go-instrumentation

OpenTelemetry Auto Instrumentation using eBPF

Runssource: GitHubhomepageCApache-2.0archived upstreamcommit 24123c2a5d46

C, Apache-2.0 licensed. The project labels itself: ebpf, go, golang, instrumentation, metrics, observability, telemetry and tracing.

opentelemetry-go-instrumentation runs. An Argusic agent installed it in 6 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

OpenTelemetry Go Automatic Instrumentation builds from source, the CLI binary (80MB) compiles and prints usage text, and all 27+ test packages across cli, sdk, internal/pkg pass with 0 failures; the tool is ready for use targeting Go processes via eBPF.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.13 (measured)
recorded runs
2
last tested
stars
1,039
forks
158
open issues
135
watchers
28
size
30 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing opentelemetry-go-instrumentation, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Go compiler (Go 1.25.0) not installed in container1 minute
  • BPF .o embed files missing - generated bpf_x86_bpfel.go files reference //go:embed bpf_x86_bpfel.o but those .o files didn't exist1 minute
Install time
6 minutes
Cold machine to finish
7 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
go test ./cli/... ./internal/... ./sdk/... ./... all passed (27+ packages, 0 failures); binary at /tmp/otel-go-instrumentation --help exits 0 showing usage; binary is 80MB
Model tokens used
108,969
Exact commit tested
24123c2a5d46
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

ok    go.opentelemetry.io/auto/internal/pkg/instrumentation/bpf/net/http/client  (cached)
--- PASS: TestProbeConvertEvent (0.00s)
ok    go.opentelemetry.io/auto/internal/pkg/instrumentation/bpf/net/http/server  (cached)
exec
/bin/sh -lc 'cd /work/repo/sdk && export PATH="/tmp/golang-install/go/bin:$PATH" && timeout 120 go …
 succeeded in 118ms:
ok    go.opentelemetry.io/auto/sdk/internal/telemetry  (cached)
ok    go.opentelemetry.io/auto/sdk  (cached)
All systems go. Here's the final report:
tokens used
108,969
All systems go. Here's the final report:

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 6 minutes, faster than the median of the 3 comparable projects Argusic has measured.
  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 4 ebpf projects Argusic has installed and timed, opentelemetry-go-instrumentation was the 1st fastest to reach a running state, and 2 of 4 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 6 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.13
Argusic Runner1/3Runs with mocks92.000.08

Topics (from GitHub)

ebpfgogolanginstrumentationmetricsobservabilitytelemetrytracing

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/opentelemetry-go-instrumentation.svg)](https://argusic.com/subject/opentelemetry-go-instrumentation)

Questions

Does opentelemetry-go-instrumentation run?
Yes. opentelemetry-go-instrumentation runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test opentelemetry-go-instrumentation?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 24123c2a5d46. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test opentelemetry-go-instrumentation?
The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does opentelemetry-go-instrumentation take to install?
6 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does opentelemetry-go-instrumentation need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing opentelemetry-go-instrumentation?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does opentelemetry-go-instrumentation compare with the alternatives?
Of the 4 ebpf projects Argusic has installed and timed, opentelemetry-go-instrumentation was the 1st fastest to reach a running state, and 2 of 4 reached one at all.
Where is the evidence for opentelemetry-go-instrumentation?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion