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 45 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The project compiles, the binary runs and processes real data end-to-end: demo_logs source reads events, console and blackhole sinks receive them, and 499 unit tests pass in 26 seconds. 3 pre-existing tests fail due to a missing external secrets-exec binary.
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.
- libclang.so not found - required by bindgen crate20 minutes
- Full binary linking OOM (SIGKILL)10 minutes
- Rust toolchain not installed2 minutes
- unzip not available for protoc extraction2 minutes
- Disk full during build (40GB filesystem)2 minutes
- 3 pre-existing test failures in secrets::exec::tests (missing external binary)
- Install time
- 45 minutes
- Cold machine to finish
- 71 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- cargo test --no-default-features --features sources-demo_logs,sinks-console,sinks-blackhole,transforms-sample exited 0 with 499 passed, 3 pre-existing failures; ./target/debug/vector --config test_config.yaml ran end-to-end generating 3 JSON events and terminating with exit 0; ./target/debug/vector --version returned 'vector 0.59.0-dev-custom-3ce1054 (x86_64-unknown-linux-gnu debug=full)'
- Model tokens used
- 682,882
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
5. **Disk full** - Had to clean up cached artifacts (~2 min) 6. **3 pre-existing test failures** in `secrets::exec::tests` - require a missing external binary, … tokens used 682,882 The pipeline works correctly. Let me compile the final report. **Errors encountered:** 1. **Rust not installed** - Installed via rustup (~2 min) 2. **`unzip` not available for protoc** - Used Python to extract (~2 min) 3. **`libclang.so` not found** - Downloaded CLang+LLVM 17.0.6 for Ubuntu 22.04, but it required `li… 4. **OOM/linker failure** on full build - Binary linking for the full default feature set gets SIGK… 5. **Disk full** - Had to clean up cached artifacts (~2 min) 6. **3 pre-existing test failures** in `secrets::exec::tests` - require a missing external binary, …
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 6 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.
What did not, or is not known
- Took 45 minutes to install, slower than the median of the 37 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 38 agent projects Argusic has installed and timed, vector was the 36th fastest to reach a running state, and 29 of 38 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 45 minutes, hitting 6 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. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test vector?
- The run that produced this verdict cost $0.23: 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?
- 45 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?
- 6 things broke in the recorded run, and 6 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 38 agent projects Argusic has installed and timed, vector was the 36th fastest to reach a running state, and 29 of 38 reached one at all.
- Where is the evidence for vector?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.