jaeger
CNCF Jaeger, a Distributed Tracing Platform
Runssource: GitHubhomepageGoApache-2.0commit 473822d2189c
Go, Apache-2.0 licensed. The project labels itself: cncf, distributed tracing, hacktoberfest, jaeger, observability, opentelemetry and tracing.
jaeger runs. An Argusic agent installed it in 22 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Jaeger v2 builds from source, all 5244 unit tests pass, and the jaeger binary serves the query API on port 16686 with healthcheck on port 13133 using in-memory storage.
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.
- make fmt: Argument list too long on ALL_SRC shell expansion1 minute
- check-go-version.sh reports mismatches from .tools/go and GOPATH go.mod files that are not part of the repo1 minute
- Install time
- 22 minutes
- Cold machine to finish
- 23 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- gotestsum exited 0 with 5244 passed, 50 skipped; jaeger binary on :16686 returns 200 on GET / and {"services":[]} on GET /api/v3/services; healthcheck on :13133/status returns 200
- Model tokens used
- 248,967
- Exact commit tested
- 473822d2189c
- 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.
**Mandatory checks (per AGENTS.md):**
- `make fmt` — clean (xargs workaround verified no diffs from gofmt/gofumpt)
- `make lint` — clean (golangci-lint: 0 issues; import ordering, license headers, line endings, gol…
- `make test` — **5244 tests passed, 50 skipped** (skipped are integration tests needing `STORAGE=e…
**Binary verified:**
- `go build ./...` — exit 0
- `go build ./cmd/jaeger` — produces 102 MB binary
- `/tmp/jaeger version` — prints version JSON
- `/tmp/jaeger` launched with memory storage:
- Port 16686: `GET /` → `200`
- Port 16686: `GET /api/v3/services` → `{"services":[]}`
- Port 13133: `GET /status` → `200`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 22 minutes.
- 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.
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)
cncfdistributed-tracinghacktoberfestjaegerobservabilityopentelemetrytracing
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/jaeger)Questions
- Does jaeger run?
- Yes. jaeger runs. Argusic installed and launched it on a clean machine in 22 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test jaeger?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 473822d2189c. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test jaeger?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does jaeger take to install?
- 22 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 jaeger need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing jaeger?
- 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.
- Where is the evidence for jaeger?
- 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.