influxdb

Scalable datastore for metrics, events, and real-time analytics

Could not verifysource: GitHubhomepageRustApache-2.0commit 693b1fd1b96c

Rust, Apache-2.0 licensed. The project labels itself: database, go, influxdb, metrics, monitoring, react, rust and time series.

Argusic could not get influxdb running. An Argusic agent hit no errors on a clean machine with no GPU, and the whole session was recorded.

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 20 of 100 (the mean of this project's run scores).

At a glance

verdict
Could not verify
Argusic Score
20 / 100
cost of the verifying run
$0.29 (measured)
recorded runs
2
last tested
stars
31,755
forks
3,717
open issues
2,183
watchers
702
size
209 MB
created
last push

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.

Cold machine to finish
73 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
Exact commit tested
693b1fd1b96c
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.

Install time
the run did not report one
How the result was proved
runs before 2026-09-07 did not record the command used to check the result
Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Model tokens used
not recorded for this run
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
Whether it works at all
this run verified nothing, so this page makes no claim either way

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

   Compiling influxdb3_query_executor v3.11.0-nightly (/work/repo/influxdb3_query_executor)
   Compiling influxdb3_commands v3.11.0-nightly (/work/repo/influxdb3_commands)
   Compiling influxdb3 v3.11.0-nightly (/work/repo/influxdb3)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 21.67s
The workspace builds successfully. Now let me run the tests.
exec
/bin/sh -lc '. "$HOME/.cargo/env" && export PATH="$HOME/protoc/bin:$PATH" && export LIBRARY_PATH=/t…
2026-09-07T20:28:31.860275Z ERROR codex_rollout::recorder: rollout writer failed for /home/runner/.…
2026-09-07T20:28:31.865535Z ERROR codex_core::session: failed to record rollout items: thread-store…
2026-09-07T20:28:31.869842Z ERROR codex_core::session: failed to record rollout items: thread-store…
2026-09-07T20:28:31.871251Z ERROR codex_core::session: failed to record rollout items: thread-store…
 succeeded in 242845ms:

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

  • Nothing broke on the way: zero errors between clone and running.
  • 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

  • An agent with no time limit did not get it running.

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.

  • hertzbeat verified to run · Java · 3 shared topics
  • hyperdx verified to run · TypeScript · 2 shared topics
  • crate verified to run · Java · 2 shared topics
  • arcadedb verified to run · Java · 2 shared topics
  • tsink verified to run · Rust · 2 shared topics

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Did not run20.000.29
Argusic Runner1/3Did not run20.000.45

Topics (from GitHub)

databasegoinfluxdbmetricsmonitoringreactrusttime-series

Embed the badge

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

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

Questions

Does influxdb run?
Argusic could not verify that influxdb runs. Argusic installed and launched it on a clean machine, hitting 0 errors on the way, and recorded the session.
How did Argusic test influxdb?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 693b1fd1b96c. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test influxdb?
The run that produced this verdict cost $0.29: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
Does influxdb need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing influxdb?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for influxdb?
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.

Discussion