thanos
Highly available Prometheus setup with long term storage capabilities. A CNCF Incubating project.
Runssource: GitHubhomepageGoApache-2.0commit c1cba09dd1b1
Go, Apache-2.0 licensed. The project labels itself: cncf, go, google cloud storage, hacktoberfest, high availability, metrics, monitoring and observability.
thanos runs. An Argusic agent installed it in 20 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 thanos binary builds and runs: its query component answered HTTP 200 on /-/, served thanos_build_info metrics, resolved a real gRPC store.LabelNames call, and the filesystem object store round-tripped uploaded data, while the unit-test suite passed in every package except pkg/reloader, which cannot run in this container because the kernel refuses to create inotify instances (EMFILE).
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.
- make test-local: pkg/reloader TestReloader_ConfigRollback failed: create watcher: too many open files (fsnotify.NewWatcher EMFILE)18 minutes
- Go toolchain missing (go: not found); README requires Go 1.26.x; no root to apt-install8 minutes
- thanos query process exited when its spawning exec session ended, so gRPC store RPC verification first failed with connection refused on 127.0.0.1:191934 minutes
- Install time
- 20 minutes
- Cold machine to finish
- 21 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- thanos --version printed 'thanos, version 0.43.0-dev (branch: HEAD, revision: c1cba09dd1b175b0c8824f298f337b8092a47c05)... go version: go1.27.3'; curl -s -o /dev/null -w %{http_code} http://127.0.0.1:19192/-/healthy returned 200; custom Go client called gRPC store.LabelNames on 127.0.0.1:19193 and printed 'grpc store.LabelNames ok names=0'; filesystem bucket Upload+Get printed 'objstore upload+read ok bytes=12 content="hello-thanos"'; 'make test-local' printed 'FAIL github.com/thanos-io/thanos/pkg/reloader' only, with every other listed package 'ok'
- Model tokens used
- 331,629
- Exact commit tested
- c1cba09dd1b1
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
tags: netgo,slicelabels
The repo is clean (no tracked changes). The query server is still up — let me reconfirm and then cl…
exec
/bin/sh -lc "curl -s -o /dev/null -w \"final healthy check: %{http_code}\\n\" http://127.0.0.1:1919…
succeeded in 0ms:
final healthy check: 200
succeeded in 17374ms:
^C
All done. Here is the report.
tokens used
331,629
All done. Here is the report.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 20 minutes.
- Recovered from all 3 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.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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)
cncfgogoogle-cloud-storagehacktoberfesthigh-availabilitymetricsmonitoringobservabilityprometheusprometheus-ha-pairsprometheus-setups3storagethanos
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/thanos)Questions
- Does thanos run?
- Yes. thanos runs. Argusic installed and launched it on a clean machine in 20 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test thanos?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c1cba09dd1b1. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test thanos?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does thanos take to install?
- 20 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 thanos need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing thanos?
- 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 thanos?
- 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.