coroot
Coroot is an open-source observability and APM tool with AI-powered Root Cause Analysis. It combines metrics, logs, traces, continuous profiling, and SLO-based alerting with predefined dashboards and inspections.
Runssource: GitHubhomepageGoApache-2.0commit d40dd882e6dd
Go, Apache-2.0 licensed. The project labels itself: ai, alerting, apm, dashboard, database monitoring, distributed tracing, ebpf and metrics.
coroot runs. An Argusic agent installed it in 7 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Coroot binary builds, frontend static assets compile, all Go tests pass (18 packages ok, 0 failures), and the server starts on port 8090 responding HTTP 200 on its root and API endpoints.
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.
- Frontend static directory missing - main.go embeds 'static' but front/dist did not exist2 minutes
- Go 1.25.5 required by go.mod but Go not installed in container1 minute
- serialize-javascript v7 uses crypto.getRandomValues() which is undefined in webpack's build context on Node 181 minute
- liblz4-dev not installed - CGo dependency of DataDog/golz4 needs lz4.h and lz4hc.h headers1 minute
- liblz4.so symlink missing - only liblz4.so.1 present, linker requires liblz4.so1 minute
- Install time
- 7 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- go test ./... exited 0 with all packages passing (cache, cache/chunk, clickhouse, collector, db, model, prom, rbac, timeseries, utils, watchers). Server started and returned HTTP 200 on both / and /api/.
- Model tokens used
- 100,082
- Exact commit tested
- d40dd882e6dd
- 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.
? github.com/coroot/coroot/front/node_modules/flatted/golang/pkg/flatted [no test files] ? github.com/coroot/coroot/grpc [no test files] ok github.com/coroot/coroot/model (cached) ? github.com/coroot/coroot/notifications [no test files] ok github.com/coroot/coroot/prom (cached) ok github.com/coroot/coroot/rbac (cached) ? github.com/coroot/coroot/stats [no test files] ok github.com/coroot/coroot/timeseries (cached) ok github.com/coroot/coroot/utils (cached) ok github.com/coroot/coroot/watchers (cached) tokens used 100,082
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.
- Recovered from all 5 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
- Took 7 minutes to install, slower than the median of the 55 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 56 ai projects Argusic has installed and timed, coroot was the 32nd fastest to reach a running state, and 43 of 56 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 7 minutes after the clone.
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)
aialertingapmdashboarddatabase-monitoringdistributed-tracingebpfmetricsmicroservicemonitoringobservabilityprometheusservice-mapslosretracing
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/coroot)Questions
- Does coroot run?
- Yes. coroot runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test coroot?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d40dd882e6dd. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test coroot?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does coroot 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 coroot need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing coroot?
- 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.
- How does coroot compare with the alternatives?
- Of the 56 ai projects Argusic has installed and timed, coroot was the 32nd fastest to reach a running state, and 43 of 56 reached one at all.
- Where is the evidence for coroot?
- 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.