sloth
🦥 Easy and simple Prometheus SLO (service level objectives) generator
Runs with mockssource: GitHubhomepageGoApache-2.0commit 8a3be4fab79d
Go, Apache-2.0 licensed. The project labels itself: alerting, alerts, autogenerates prometheus slo, controller, google slo, kubernetes, metrics and monitoring.
sloth runs, with stand-ins for the services it depends on. An Argusic agent installed it in 2 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Sloth CLI is fully functional: generate, validate, server (with fake Prometheus backend), and version commands all work. The test suite passes completely (32 of 32 test packages).
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.
- Go compiler not installed in container2 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- go run ./cmd/sloth version returned "dev"; go run ./cmd/sloth generate -i examples/getting-started.yml produced valid Prometheus SLO rules; go run ./cmd/sloth validate -i examples/getting-started.yml returned "Validation succeeded"; go test -race across 32 packages returned 0 failures; server started with --fake-prometheus, health endpoint returned HTTP 200 "ok", app root returned 303, UI returned 307
- Model tokens used
- 72,095
- Exact commit tested
- 8a3be4fab79d
- 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.
tokens used 72,095 Here's the summary of what was done: ## Work Done **Environment setup:** This container had no Go compiler. I extracted `golang-1.22-go` from the Ubu… **Verification results:** - `sloth version` → printed `dev` - `sloth generate -i examples/getting-started.yml` → produced complete Prometheus SLO rules (SLI re… - `sloth validate -i examples/getting-started.yml` → output "Validation succeeded" - `sloth server --fake-prometheus` → started and served HTTP 200 on `/status`, 303 on `/`, 307 on `… - Unit tests: **32 of 32 test packages passed**, 0 failures, 0 errors **One error encountered and fixed:** missing Go compiler (resolved by extracting from the golang-1.…
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 2 minutes, faster than the median of the 4 comparable projects Argusic has measured.
- Recovered from all 1 error 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 5 alerting projects Argusic has installed and timed, sloth was the 1st fastest to reach a running state, and 3 of 5 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.04 |
Topics (from GitHub)
alertingalertsautogenerates-prometheus-slocontrollergoogle-slokubernetesmetricsmonitoringobservabilityoncallopenslooperatorprometheusprometheus-operatorservice-levelservice-level-objectiveslaslislo
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/sloth)Questions
- Does sloth run?
- sloth runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test sloth?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8a3be4fab79d. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test sloth?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does sloth 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 sloth need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing sloth?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does sloth compare with the alternatives?
- Of the 5 alerting projects Argusic has installed and timed, sloth was the 1st fastest to reach a running state, and 3 of 5 reached one at all.
- Where is the evidence for sloth?
- 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.