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 18 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
jaeger (v2) builds from source, passes 5244 unit tests with 0 lint issues, and the all-in-one binary starts and serves HTTP on port 16686
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.
- Install time
- 18 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- make test exited 0, 5244 passed 50 skipped; curl http://localhost:16686/ returned HTTP 200
- Model tokens used
- 49,122
- 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.
**No errors encountered.** The repository builds, passes its full unit test suite, and the primary … tokens used 49,122 All checks pass. Here's my final report: - **Go 1.27.0** was not pre-installed in the container; I downloaded and set it up. - **`make install-tools`** → built all required tooling (gotestsum, golangci-lint, gofumpt, etc.). - **`make fmt`** → passed, no changes needed. - **`make lint`** → 0 issues after full analysis. - **`make test`** → **5244 tests passed**, 50 skipped (all skips are integration tests requiring ex… - **`go build ./cmd/jaeger`** → binary compiled successfully. - **`go run ./cmd/jaeger`** → Jaeger started, listening on ports 16686/4317/4318/6831/6832/14250/14… **No errors encountered.** The repository builds, passes its full unit test suite, and the primary …
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 18 minutes.
- Nothing broke on the way: zero errors between clone and running.
- 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.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- Following its own README: the documented path worked with nothing to fix.
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 18 minutes, hitting 0 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. 2 attempts are 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.08: 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?
- 18 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?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for jaeger?
- 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.