odigos
Distributed tracing without code changes. 🚀 Instantly monitor any application using OpenTelemetry and eBPF
Runs with mockssource: GitHubhomepageGoApache-2.0commit ab65b465b4f8
Go, Apache-2.0 licensed. The project labels itself: dotnet, ebpf, go, java, javascript, kubernetes, logs and metrics.
odigos runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Odigos monorepo Go modules common, api, and status each pass their test suites. The CLI binary compiles and runs. The frontend webapp builds as a static Next.js site. The autoscaler, k8sutils, and collector configgrpc module tests cannot execute due to missing kubebuilder/etcd infrastructure or build toolchain issues.
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 92 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.
- Autoscaler tests require kubebuilder/etcd which is not available
- Collector configgrpc tests fail with gcController reference error
- k8sutils tests can't be discovered by 'go test' due to source files under pkg/ not at module root
- Install time
- 7 minutes
- Cold machine to finish
- 28 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- go test -tags=embed_manifests ./common returned ok (0.007s), ./api returned ok (0.021s), ./status returned ok (0.007s); go build -tags=embed_manifests ./cli produced executable /tmp/odigos (107MB) which runs 'odigos version' and 'odigos --help' correctly; npm run build in frontend/webapp completed with static export
- Model tokens used
- 211,459
- Exact commit tested
- ab65b465b4f8
- 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.
- `./common` — **ok** (PASS, all tests pass including config tests, profiling tests, etc.) - `./api` — **ok** (PASS, render_test.go passes with `-tags=embed_manifests`) - `./status` — **ok** (PASS, message_test.go passes) - `./k8sutils` — tests cannot run directly because the module has no `.go` files at the root level … - `./collector/config/configgrpc` — FAIL: build error `link: github.com/odigos-io/go-rtml: invalid … - `./autoscaler` — FAIL: requires `/usr/local/kubebuilder/bin/etcd` (kubebuilder infrastructure not… **Key observations**: - The `common` module has 26 test files spanning config tests, profiling, language detection, span … - The API test (`render_test.go`) passes with the `embed_manifests` tag. - The `status` module test passes. - The CLI binary was successfully compiled and produces correct output (no Kubernetes cluster found… - The frontend webapp builds successfully as a Next.js static site.
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
- Installed in 7 minutes.
- Recovered from all 3 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.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 | 1/3 | Runs with mocks | 92.00 | 0.14 |
Topics (from GitHub)
dotnetebpfgojavajavascriptkuberneteslogsmetricsmonitoringnodejsobservabilityopentelemetryotelpythontraces
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/odigos)Questions
- Does odigos run?
- odigos runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test odigos?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ab65b465b4f8. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test odigos?
- 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 odigos take to install?
- 7 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 odigos need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing odigos?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for odigos?
- 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.