Yes. hertzbeat runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 5 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. 2 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.36: 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?

6.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 hertzbeat need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing hertzbeat?

5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for hertzbeat?

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.

hertzbeat

An AI-powered next-generation open source real-time observability system.

Runssource: GitHub homepageJavaApache-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 6.2 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Apache HertzBeat 2.0-SNAPSHOT builds with JDK 25, all 1930 unit tests pass, and the Spring Boot application starts on port 1157 with Tomcat, H2 database, DuckDB storage, Netty scheduler on 1158, 37 collect strategies registered, MCP server enabled, and 39 JPA repositories loaded.
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

verdict: Runs
Argusic Score: 100 / 100
cost of the verifying run: $0.36 (measured)
recorded runs: 2
last tested: 2026-09-16
stars: 7,401
forks: 1,335
open issues: 326
watchers: 71
size: 357 MB
created: 2022-02-04
last push: 2026-09-21

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-22. 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.

Time lost to each failure while testing hertzbeat, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

JDK 17 installed initially, but project requires JDK 25+2.5 minutes
Maven not pre-installed1 minute
Maven checkstyle plugin XML parse error on 'compile' phase0.5 minutes
H2 database file locking between test runs caused ApplicationContext failures in dao tests0.5 minutes
StartupMysqlR2dbcCompatibilityTest requires Docker for Testcontainers0.5 minutes

Install time: 6 minutes
Cold machine to finish: 86 minutes
Errors hit and fixed: 5 hit, 5 fixed with no human help
How the result was proved: mvnw test across 15 modules returned BUILD SUCCESS with 1930 tests passed; curl -s -o /dev/null -w '%{http_code}' http://localhost:1157/actuator/health returned 401 (auth layer working); curl -s -o /dev/null -w '%{http_code}' http://localhost:1157/ returned 404 (server alive, no frontend); app banner printed with 'Started HertzBeatApplication in X seconds'
Model tokens used: 465,615
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.

echo "App started and responded on port 1157"
echo "=== STATS ==="
echo "619+131+100+3+473+4+22+99+334+62+83 = 1930 unit tests passed (with 4 skipped)"' in /work/repo
 succeeded in 6911ms:
0
=== APP RESPONSE ===
App started and responded on port 1157
=== STATS ===
619+131+100+3+473+4+22+99+334+62+83 = 1930 unit tests passed (with 4 skipped)
2026-09-16T06:45:32.581196Z ERROR codex_core::session: failed to record rollout items: thread 01a0a…
tokens used
465,615

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 5 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 did not, or is not known

Took 6.2 minutes to install, slower than the median of the 32 comparable projects Argusic has measured.

Of the 33 agent projects Argusic has installed and timed, hertzbeat was the 18th fastest to reach a running state, and 25 of 33 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 6.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

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Runs	100.00	0.36	2026-09-16 06:45 UTC
Argusic Runner	1/3	Runs	100.00	0.16	2026-09-03 11:16 UTC

Topics (from GitHub)

agent ai alerting database grafana linux llm logs metrics monitor monitoring notifications observability prometheus self-hosted server status status-page uptime zabbix

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/hertzbeat.svg)](https://argusic.com/subject/hertzbeat)

Questions

Does hertzbeat run?: Yes. hertzbeat runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 5 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. 2 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.36: 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?: 6.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 hertzbeat need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing hertzbeat?: 5 things broke in the recorded run, and 5 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 33 agent projects Argusic has installed and timed, hertzbeat was the 18th fastest to reach a running state, and 25 of 33 reached one at all.
Where is the evidence for hertzbeat?: 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.