streampipes

Apache StreamPipes - A self-service (Industrial) IoT toolbox to enable non-technical users to connect, analyze and explore IoT data streams.

Runssource: GitHubhomepageJavaApache-2.0commit 16aa0fb3a65d

Java, Apache-2.0 licensed. The project labels itself: analytics, dashboard, edge, iiot, iot, iot analytics, iot platform and microservices.

streampipes runs. An Argusic agent installed it in 43 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Maven builds all non-integration modules successfully, 1073 backend unit tests pass with zero failures, the Angular UI builds to dist, and the backend jar starts and initializes Tomcat on port 8030 before stopping because the CouchDB service is not available 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 60 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
60 / 100
cost of the verifying run
$0.14 (measured)
recorded runs
2
last tested
stars
763
forks
254
open issues
68
watchers
26
size
334 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.

Time lost to each failure while testing streampipes, 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.

  • No JDK 25 or Maven installed; Java and Maven were absent8 minutes
  • Backend JAR initialization failed: host 'couchdb' unresolvable (CouchDB service absent)5 minutes
  • Bundled Node.js v18 was too old for Angular (minimum v22.22.3)4 minutes
  • pip3 install poetry blocked by PEP 668 externally-managed environment3 minutes
  • UI lint reports 5 pre-existing unused-variable errors (ng lint app)
Install time
43 minutes
Cold machine to finish
45 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
mvn clean verify -DskipTests exited 0 (BUILD SUCCESS); mvn test -pl '!streampipes-integration-tests' -am exited 0 with 1073 tests, 0 failures; npm ci && npm run build exited 0 producing ui/dist/streampipes/ui/browser/index.html; npx prettier --check . reported all files formatted; java -jar streampipes-core.jar started Tomcat 11.0.15 port 8030 and printed v0.99.0-SNAPSHOT before crashing on 'couchdb' name resolution
Model tokens used
721,681
Exact commit tested
16aa0fb3a65d
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.

**What was verified:**
- `mvn clean verify -DskipTests` (excluding integration tests) → `BUILD SUCCESS`.
- `mvn test -pl '!streampipes-integration-tests' -am` → `BUILD SUCCESS`, **1073 tests, 0 failures, …
- `cd ui && npm ci && npm run build` → SUCCESS, UI output at `ui/dist/streampipes/ui/browser/index.…
- `npx prettier --check .` in `ui/` → "All matched files use Prettier code style!"
- `java -jar streampipes-service-core/target/streampipes-core.jar` → launched, printed version `v0.…
**Errors hit and fixes:**
1. No JDK 25 / Maven present → downloaded both to user space (fixed).
2. Node v18 too old for Angular (min v22.22.3) → downloaded Node v22.23.3 (fixed).
3. `pip3 install poetry` blocked by PEP 668 (externally-managed env) → could not install (no root);…
4. Backend cannot complete startup without CouchDB, NATS, and InfluxDB (need Docker, not available)…
5. Pre-existing UI lint errors (`npx ng lint app`: 5 unused-variable errors in `src/app/...`) — exi…

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 43 minutes to install, slower than the median of the 19 comparable projects Argusic has measured.

Of the 20 analytics projects Argusic has installed and timed, streampipes was the 19th fastest to reach a running state, and 15 of 20 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.14
Argusic Runner1/3Did not run20.000.33

Topics (from GitHub)

analyticsdashboardedgeiiotiotiot-analyticsiot-platformmicroservicesopcuas7self-servicestream-processing

Embed the badge

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

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

Questions

Does streampipes run?
Yes. streampipes runs. Argusic installed and launched it on a clean machine in 43 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test streampipes?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 16aa0fb3a65d. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test streampipes?
The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does streampipes take to install?
43 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 streampipes need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing streampipes?
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 streampipes compare with the alternatives?
Of the 20 analytics projects Argusic has installed and timed, streampipes was the 19th fastest to reach a running state, and 15 of 20 reached one at all.
Where is the evidence for streampipes?
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