qtap
Qtap: An eBPF agent that captures pre-encrypted network traffic, providing rich context about egress connections and their originating processes.
Runssource: GitHubhomepageCApache-2.0commit 6d7dfa743c9a
C, Apache-2.0 licensed. The project labels itself: containers, developer tools, ebpf, go, golang, kubernetes, libbpf and linux.
qtap runs. An Argusic agent installed it in 14 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Go 1.27.1 was downloaded and installed; go build produces a working qtap binary at /work/repo/bin/qtap that responds to --help and --version; the test suite passes on 49 of 51 packages (only pkg/egress IPv6 tests fail because this container has IPv6 disabled)
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 100 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.
- Go 1.27.1 not pre-installed; had to download tarball3 minutes
- clang not installed (required for eBPF code generation)1 minute
- JVM embedded dist/ files missing (5 files for go:embed)1 minute
- IPv6 disabled in container - 4 egress tests fail with 'bind: cannot assign requested address' for tcp61 minute
- Install time
- 14 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- go test -count=1 ./... -> 49 packages ok, 1 package FAIL (pkg/egress with 4 IPv6 failures); /work/repo/bin/qtap --version printed 'qtap version dev'
- Model tokens used
- 163,310
- Exact commit tested
- 6d7dfa743c9a
- 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.
FAIL github.com/qpoint-io/qtap/pkg/egress 0.948s Now I have all the data. Let me compile the final report exec /bin/sh -lc 'echo "Start time: $(date -d @1791400800 +%s 2>/dev/null || echo 1791400800)" && echo "… succeeded in 0ms: Start time: 1791400800 Current time: 1791401642 Elapsed (est): 842 seconds Here's the final report: tokens used 163,310 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 14 minutes.
- Recovered from all 4 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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
Topics (from GitHub)
containersdeveloper-toolsebpfgogolangkuberneteslibbpflinuxobservabilitysecurity
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/qtap)Questions
- Does qtap run?
- Yes. qtap runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test qtap?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6d7dfa743c9a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test qtap?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does qtap take to install?
- 14 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 qtap need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing qtap?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for qtap?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.