beyla
eBPF-based autoinstrumentation of web applications and network metrics
Could not verifysource: GitHubhomepageGoApache-2.0commit d6e1d67280ea
Go, Apache-2.0 licensed. The project labels itself: ebpf, metrics gathering, observability and traces.
Argusic could not get beyla running. An Argusic agent installed it in 42 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Prebuilt Beyla v3.36.0 binary launches and prints version. 11 Go test packages pass. Example HTTP service compiles. Source build fails due to missing eBPF bytecode generation requiring Docker or clang >=19.
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 20 of 100 (the mean of this project's run scores).
At a glance
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- BPF .o bytecode files missing from vendor directory (go:embed targets)13 minutes
- Git submodule .obi-src empty at checkout10 minutes
- Source build fails with 21+ undefined BPF-generated type errors10 minutes
- Disk full during LLVM extraction (7.8G total, 3.2G trash remaining)7 minutes
- Go not pre-installed in container2 minutes
- Install time
- 42 minutes
- Cold machine to finish
- 44 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- /tmp/beyla --help prints usage; /tmp/beyla v3.36.0 starts, reports Version=v3.36.0 Revision=f956ea2 SDK=1.46.0, exits with config validation error. go test -mod=vendor on 11 eBPF-independent packages: all passed with 0 failures. Example HTTP service builds.
- Model tokens used
- 501,200
- Exact commit tested
- d6e1d67280ea
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
{'msg': 'Disk full during LLVM extraction (7.8G total, 3.2G trash remaining)', 'fix': 'Clea…
],
'test_depth': 'tier2_mock',
'verified_how': '/tmp/beyla --help prints usage; /tmp/beyla v3.36.0 starts, reports Version=v3.…
'final_state': 'Prebuilt Beyla v3.36.0 binary launches and prints version. 11 Go test packages …
}
print(json.dumps(result))
\"" in /work/repo
succeeded in 0ms:
{"install_succeeded": false, "launch_succeeded": true, "install_minutes": 42.0, "errors": [{"msg": …
tokens used
501,200Replay 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
- Installed in 42 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Did not run | 20.00 | 0.14 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.37 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/beyla)Questions
- Does beyla run?
- Argusic could not verify that beyla runs. Argusic installed and launched it on a clean machine in 42 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test beyla?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d6e1d67280ea. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test beyla?
- The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does beyla take to install?
- 42 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 beyla need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing beyla?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for beyla?
- 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.