updo
Uptime monitoring CLI tool with alerting and advanced settings
Runssource: GitHubhomepageGoMITcommit 97998eae455a
Go, MIT licensed. The project labels itself: cli, go, grafana, monitoring, observability, prometheus, termui and tui.
updo runs. An Argusic agent installed it in 2 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Updo builds with Go 1.27.4, all 10 test packages pass, the binary monitors real URLs with correct HTTP status/response time/SSL tracking displayed in simple, TUI, and JSON log modes, and the config file with 7 concurrent targets with diverse settings (assertions, headers, POST, redirect handling) executes correctly.
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.
- Go 1.27.4 was not installed in the container1 minute
- zip command not found for Lambda ZIP creation1 minute
- Install time
- 2 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- go test ./... exited 0 with 10 packages passed; ./updo monitor --simple -c 2 -r 2 https://httpbin.org/get returned 2 successful checks with 200 status, 100% uptime, 358/370ms response times, SSL expiry; --log flag produced valid JSON structured logs; --config example-config.toml ran 7 concurrent targets with assertions, redirect handling, custom headers, text assertions; go vet ./... passed clean
- Model tokens used
- 32,533
- Exact commit tested
- 97998eae455a
- 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.
exec /bin/sh -lc 'cd /work/repo && ls -la updo aws/bootstrap aws/bootstrap.zip' in /work/repo succeeded in 0ms: -rwxrwxr-x 1 runner runner 6291580 Jan 1 1980 aws/bootstrap -rw-r--r-- 1 runner runner 2606978 Nov 18 22:17 aws/bootstrap.zip -rwxrwxr-x 1 runner runner 20353287 Nov 18 22:17 updo OK, let me just move on - those build artifacts are fine. Let me compile my final assessment. tokens used 32,533 OK, let me just move on - those build artifacts are fine. Let me compile my final assessment.
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 2 minutes, faster than the median of the 126 comparable projects Argusic has measured.
- 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 MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
Of the 127 cli projects Argusic has installed and timed, updo was the 40th fastest to reach a running state, and 115 of 127 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 2 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)
cligografanamonitoringobservabilityprometheustermuituiuptime
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/updo)Questions
- Does updo run?
- Yes. updo runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test updo?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 97998eae455a. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test updo?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does updo take to install?
- 2 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 updo need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing updo?
- 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.
- How does updo compare with the alternatives?
- Of the 127 cli projects Argusic has installed and timed, updo was the 40th fastest to reach a running state, and 115 of 127 reached one at all.
- Where is the evidence for updo?
- 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.