robusta
Better Prometheus alerts for Kubernetes - smart grouping, AI enrichment, and automatic remediation
Runs with mockssource: GitHubhomepagePythonMITcommit 1207e8e2c34f
Python, MIT licensed. The project labels itself: alerting, alertmanager, automation, containers, dashboard, devops, docker and grafana.
robusta runs, with stand-ins for the services it depends on. An Argusic agent installed it in 4.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.
All 422 unit tests pass on Python 3.12, the Flask web app loads and accepts connections on port 9876 returning 500 on /healthz (expected: healthz requires Web.init which needs a Kubernetes cluster), and 3 infrastructure-dependent tests (k8s_utils, kind_cluster) are skipped as expected without a Kubernetes cluster.
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.
- Python version constraint too strict: pyproject.toml required >=3.10, <3.12 but only Python 3.12 is available in container1 minute
- Missing dependency 'strenum' not listed in pyproject.toml, causing ModuleNotFoundError on import0.5 minutes
- get_all_namespace_data() in api_client_utils.py only caught ApiException but connection refused errors from urllib3 are not ApiException, causing test failures (17 scope_matching tests) and crash when no Kubernetes cluster is present0.5 minutes
- test_discovery_recovery_on_failure only patched kubernetes.client.CoreV1Api.list_node but discovery_process calls AppsV1Api.list_deployment_for_all_namespaces first, hitting real connection error0.5 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- poetry run pytest tests/ -k 'not test_helm_chart and not test_k8s_utils and not test_fixtures' --tb=line -q returned: 422 passed, 11 skipped, 13 deselected in 14.71s
- Model tokens used
- 93,886
- Exact commit tested
- 1207e8e2c34f
- 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.
+ kubernetes.client.AppsV1Api.list_deployment_for_all_namespaces = _patched def test_discovery_recovery_on_failure(): exec /bin/sh -lc 'export PATH="$HOME/.local/bin:$PATH" && cd /work/repo && poetry run python -m pytest t… succeeded in 17046ms: ........................................................................ [ 99%] . [100%] 422 passed, 11 skipped, 13 deselected in 14.71s I have a thorough assessment. Here's the ARGUSIC_RESULT: tokens used 93,886 I have a thorough assessment. Here's the ARGUSIC_RESULT:
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 4.5 minutes, faster than the median of the 3 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 MIT, 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 4 alerting projects Argusic has installed and timed, robusta was the 2nd fastest to reach a running state, and 3 of 4 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.07 |
Topics (from GitHub)
alertingalertmanagerautomationcontainersdashboarddevopsdockergrafanakuberneteskubernetes-dashboardkubernetes-monitoringmonitoringmonitoring-toolnotificationsobservabilityprometheusprometheus-alertmanagerpythonrunbooksslack
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/robusta)Questions
- Does robusta run?
- robusta runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 5 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test robusta?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1207e8e2c34f. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test robusta?
- 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 robusta take to install?
- 4.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 robusta need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing robusta?
- 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 robusta compare with the alternatives?
- Of the 4 alerting projects Argusic has installed and timed, robusta was the 2nd fastest to reach a running state, and 3 of 4 reached one at all.
- Where is the evidence for robusta?
- 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.