hertzbeat
An AI-powered next-generation open source real-time observability system.
Runssource: GitHubhomepageJavaApache-2.0commit d5995a967511
Java, Apache-2.0 licensed. The project labels itself: agent, ai, alerting, database, grafana, linux, llm and logs.
hertzbeat runs. An Argusic agent installed it in 12 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
HertzBeat server builds, its full Maven test suite passes except one Docker-only integration test, and the assembled server runs with working JWT login and authenticated API on port 1157 in this container.
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.
- mvn test: StartupMysqlR2dbcCompatibilityTest requires Testcontainers Docker (spins up mysql:8.0.36); no docker/podman/dockerd socket and no root, so no mock can be stood up in this container.31 minutes
- Plain `java -jar apache-hertzbeat-1.9.0.jar` fails with NoClassDefFoundError: SpringApplication; package must be built via -Prelease and launched with classpath lib/* + main class.20 minutes
- No java/mvn in container and no root: README requires java25 + maven3+. Downloaded Temurin JDK 25.0.4.1 and Maven 3.9.9 to ~/tools and set JAVA_HOME/PATH.5 minutes
- Install time
- 12 minutes
- Cold machine to finish
- 37 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- mvn -DskipTests clean install BUILD SUCCESS and mvn test: 3673 tests run, 0 failures, 0 errors (1 Docker-only test errored); curl POST /api/account/auth/form -> 200 JWT; curl GET /api/monitors -H 'Authorization: Bearer <jwt>' -> 200 {"code":0,...}; curl GET /index.html -> 200; process stayed up 5+ min until graceful shutdown.
- Model tokens used
- 718,769
- Exact commit tested
- d5995a967511
- 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.
- `POST /api/account/auth/form` with `admin/hertzbeat` → HTTP 200, JWT token returned.
- `GET /api/monitors` with bearer token → HTTP 200, `{"code":0,...}`.
- `GET /index.html` → 200 (successful Angular production build of `web-app` served by the backen…
- Process stayed up 5+ min until graceful shutdown.
exec
/bin/sh -lc 'echo done' in /work/repo
succeeded in 0ms:
done
The mission is complete. Here is the final report:
tokens used
718,769
The mission is complete. Here is the final 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.
- 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 3 times, so the result is not a one-off.
What did not, or is not known
- Took 12 minutes to install, slower than the median of the 136 comparable projects Argusic has measured.
Of the 137 agent projects Argusic has installed and timed, hertzbeat was the 86th fastest to reach a running state, and 89 of 137 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.
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)
agentaialertingdatabasegrafanalinuxllmlogsmetricsmonitormonitoringnotificationsobservabilityprometheusself-hostedserverstatusstatus-pageuptimezabbix
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/hertzbeat)Questions
- Does hertzbeat run?
- Yes. hertzbeat runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test hertzbeat?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit d5995a967511. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test hertzbeat?
- The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does hertzbeat take to install?
- 12 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 hertzbeat need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing hertzbeat?
- 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.
- How does hertzbeat compare with the alternatives?
- Of the 137 agent projects Argusic has installed and timed, hertzbeat was the 86th fastest to reach a running state, and 89 of 137 reached one at all.
- Where is the evidence for hertzbeat?
- All 3 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.