Does nightingale run?

Yes. nightingale runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 5 errors on the way, and recorded the session.

How did Argusic test nightingale?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6392c79de4bf. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test nightingale?

The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does nightingale take to install?

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

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

What goes wrong when installing nightingale?

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

Where is the evidence for nightingale?

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.

nightingale

Nightingale is to monitoring and alerting what Grafana is to visualization.

Runssource: GitHub homepageGoApache-2.0commit 6392c79de4bf

Go, Apache-2.0 licensed. The project labels itself: alerting, ccf, metrics, monitoring, nightingale, observability, open falcon and time series.

nightingale runs. An Argusic agent installed it in 7.5 minutes and hit 5 errors on a clean machine with no GPU, and the whole session was recorded.

n9e server builds, starts on port 17000 with SQLite+embedded TSDB, serves SPA and REST API, authenticates root user login, responds to Prometheus queries, and exposes a built-in MCP endpoint with 30+ tools over Streamable HTTP transport.
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 88 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 88 / 100
cost of the verifying run: $0.06 (measured)
recorded runs: 2
last tested: 2026-09-26
stars: 13,312
forks: 1,781
open issues: 258
watchers: 170
size: 118 MB
created: 2020-03-03
last push: 2026-09-23

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

Go compiler not installed in container0.5 minutes
statik binary not found, fe.sh failed0.2 minutes
pkg/unit: timestamp tests fail in UTC timezone (expect Asia/Shanghai dates)
pkg/ormx, models/migrate, dskit/mysql, dskit/clickhouse, dskit/victorialogs: tests require external MySQL/Postgres/ClickHouse/VictoriaLogs services
pkg/promql: TestGetLabelsAndMetricNameWithReplace ordering issue in promql parser (pre-existing)

Install time: 8 minutes
Cold machine to finish: 13 minutes
Errors hit and fixed: 5 hit, 2 fixed with no human help
How the result was proved: curl -s -o /dev/null -w %{http_code} http://127.0.0.1:17000/ returned 200; POST /api/n9e/auth/login returned JWT for root/Admin; MCP POST /mcp with Authorization: Bearer returned tools/list with 30+ tools; /prometheus/api/v1/labels returned {"data":[],"status":"success"}; go test on 30 packages: 25 passed, 5 failed due to missing external DBs/timezone mismatch
Model tokens used: 96,358
Exact commit tested: 6392c79de4bf
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.

exec
/bin/sh -lc 'ls -lh /work/repo/n9e /work/repo/n9e-edge /work/repo/n9e-alert /work/repo/n9e-pushgw /…
 succeeded in 0ms:
-rwxrwxr-x 1 runner runner 146M Sep 26 17:47 /work/repo/n9e
-rwxrwxr-x 1 runner runner 120M Sep 26 17:55 /work/repo/n9e-alert
-rwxrwxr-x 1 runner runner  25M Sep 26 17:55 /work/repo/n9e-cli
-rwxrwxr-x 1 runner runner 120M Sep 26 17:54 /work/repo/n9e-edge
-rwxrwxr-x 1 runner runner  74M Sep 26 17:55 /work/repo/n9e-pushgw
All done. Here is the complete report.
tokens used
96,358
All done. Here is the complete 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 7.5 minutes.
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

Hit 5 errors during setup, 3 of which were not solved.

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 7.5 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	88.00	0.06	2026-09-26 17:56 UTC
Argusic Runner	1/3	Ran out of time	0.00	0.13	2026-09-26 17:43 UTC

Topics (from GitHub)

alerting ccf metrics monitoring nightingale observability open-falcon time-series tsdb

Embed the badge

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

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

Questions

Does nightingale run?: Yes. nightingale runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test nightingale?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6392c79de4bf. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test nightingale?: The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does nightingale take to install?: 7.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 nightingale need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing nightingale?: 5 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for nightingale?: 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.