vector
A high-performance observability data pipeline.
Runssource: GitHubhomepageRustMPL-2.0commit 3ce105431bed
Rust, MPL-2.0 licensed. The project labels itself: agent, cloud native, data transformation, datadog, etl, events, forwarder and hacktoberfest.
vector runs. An Argusic agent installed it in 76 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
A preserved Vector binary reports version 0.59.0-dev-custom-3ce1054, validates a YAML config, and successfully processed three sentinel log records through demo_logs, remap, and console with no stderr output.
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.
- Full default cargo build was killed by the cgroup OOM killer at the 8 GB memory limit27 minutes
- cargo build --bin vector failed in zstd-sys because libclang.so was missing6 minutes
- Four config::watcher tests failed with Too many open files when run together; the container permits only one inotify instance6 minutes
- make test using nextest failed after cargo test compilation with No space left on device4 minutes
- bindgen then failed with zstd.h:10: fatal error: stddef.h file not found2 minutes
- Three secrets::exec tests failed with No such file or directory because python was not installed under that name2 minutes
- Install time
- 76 minutes
- Cold machine to finish
- 78 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- /home/runner/.local/bin/vector --version returned vector 0.59.0-dev-custom-3ce1054 (x86_64-unknown-linux-gnu debug=full) and exited 0; vector validate exited 0; the demo_logs -> remap -> console run exited 0 with 3/3 sentinel records and 3/3 transform markers, 0 stderr bytes; cargo test sources::demo_logs exited 0 with 12 passed; cargo test --lib with only the 4 inotify watcher tests skipped exited 0 with 504 passed, 1 ignored
- Model tokens used
- 966,744
- Exact commit tested
- 3ce105431bed
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- Focused tests passed 12/12. The broader suite passed 504/504 when four inotify-bound watcher test… - Repository remains clean; only user-home tooling and temporary test files outside the repo were a… **Errors And Fixes** - `unzip: command not found`: added a Python-based `~/.local/bin/unzip`. - Missing `libclang`: extracted Ubuntu `libclang1-18` and `libllvm18` into `~/.local/libclang`; con… - Missing `stddef.h`: added GCC include paths through `BINDGEN_EXTRA_CLANG_ARGS`. - Full build OOM-killed at the 8 GB cgroup limit: rebuilt with `CARGO_BUILD_JOBS=1` and `CARGO_PROF… - `python` missing for secret tests: linked `python` to `python3`; those 3 tests then passed. - Four config-watcher tests fail when combined because the container effectively permits only one i… - Nextest’s all-feature test build exhausted the 40 GB disk. I removed generated `target/` artifact… </｜DSML｜ invoke> </｜DSML｜ calls>
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 7 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 MPL-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 76 minutes to install, slower than the median of the 137 comparable projects Argusic has measured.
Of the 138 agent projects Argusic has installed and timed, vector was the 138th fastest to reach a running state, and 92 of 138 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)
agentcloud-nativedata-transformationdatadogetleventsforwarderhacktoberfesthigh-performancelogsmetricsmonitoringobservabilitypipelinesrust-langstream-processingtelemetrytraces
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/vector)Questions
- Does vector run?
- Yes. vector runs. Argusic installed and launched it on a clean machine in 76 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test vector?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3ce105431bed. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test vector?
- The run that produced this verdict cost $1.28: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does vector take to install?
- 76 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 vector need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing vector?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does vector compare with the alternatives?
- Of the 138 agent projects Argusic has installed and timed, vector was the 138th fastest to reach a running state, and 92 of 138 reached one at all.
- Where is the evidence for vector?
- 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.