superlog
Open-source observability tool that uses AI agents to self-heal your software
Runs with mockssource: GitHubhomepageTypeScriptApache-2.0commit b6f3223ac672
TypeScript, Apache-2.0 licensed. The project labels itself: ai, llm, memory, observability, opentelemetry, react, self hosted and skills.
superlog runs, with stand-ins for the services it depends on. An Argusic agent installed it in 1.5 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
pnpm install succeeded (51s). Node v22.23.3 with pnpm 9.15.9. 143 proxy tests pass, 78 worker tests pass, ~380+ total tests pass across all packages with 0 failures. Full stack requires Docker for postgres/clickhouse/collector which is unavailable without root.
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.
- Node.js 18.19.1 was installed, project requires >=20; Docker is not available (no root), cannot run postgres/clickhouse/collector containers10 minutes
- DATABASE_URL is not set — real Postgres required for API server, web server, and most integration tests5 minutes
- 127 DB migrations (23MB) cause pglite-based migration test to timeout/run very slowly
- Docker compose unavailable — cannot start postgres, clickhouse, or collector services
- Install time
- 2 minutes
- Cold machine to finish
- 46 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- Run results: apps/proxy: 143 tests, 143 pass. apps/worker: 78 tests, 78 pass. packages/billing: 38 pass. packages/cloudflare: 19 pass. packages/fingerprint: 26 pass. packages/gcp-auth: 1 pass. packages/net-guard: 72 pass. packages/otel: 1 pass. packages/railway: 68 pass. packages/render: 20 pass. packages/telemetry-query: 11 pass, 30 skipped (need ClickHouse). packages/topology: 19 pass. apps/api: 58+ pass (unit tests only). apps/web: 55+ pass (unit/wire tests). CI workflow security test: 3 pass. All zero failures.
- Model tokens used
- 360,359
- Exact commit tested
- b6f3223ac672
- 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.
/bin/sh -lc 'export PATH=$HOME/n/bin:/work/repo/node_modules/.bin:$PATH && cd /work/repo && SECONDS… # Verify install was clean echo "Install verification:" pnpm ls --depth 0 -r 2>&1 | head -5' in /work/repo succeeded in 2330ms: Install time approximated from run Install verification: Legend: production dependency, optional only, dev only superlog /work/repo (PRIVATE) devDependencies: tokens used 360,359
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 1.5 minutes, faster than the median of the 104 comparable projects Argusic has measured.
- Recovered from all 4 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.
Of the 105 ai projects Argusic has installed and timed, superlog was the 18th fastest to reach a running state, and 72 of 105 reached one at all.
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.24 |
Topics (from GitHub)
aillmmemoryobservabilityopentelemetryreactself-hostedskillstypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/superlog)Questions
- Does superlog run?
- superlog runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test superlog?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b6f3223ac672. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test superlog?
- The run that produced this verdict cost $0.24: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does superlog take to install?
- 1.5 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 superlog need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing superlog?
- 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.
- How does superlog compare with the alternatives?
- Of the 105 ai projects Argusic has installed and timed, superlog was the 18th fastest to reach a running state, and 72 of 105 reached one at all.
- Where is the evidence for superlog?
- 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.