fluent-bit
Fast and Lightweight Logs, Metrics and Traces processor for Linux, BSD, OSX and Windows
Runssource: GitHubhomepageCApache-2.0commit 046accf6aded
C, Apache-2.0 licensed. The project labels itself: cloudnative, data collector, fluent bit, fluentd, forwarder, logging, logs and metrics.
fluent-bit runs. An Argusic agent installed it in 30 minutes and hit 5 errors on a clean machine with no GPU, and the whole session was recorded.
Fluent Bit v5.1.3 builds from source. Binary launches at /work/repo/build/bin/fluent-bit. 96/97 internal tests pass; the flb-it-network IPv6 test fails because IPv6 is disabled in the 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 96 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.
- bison not installed (required by CMake find_package)8 minutes
- m4 not installed (required for flex/bison build)7 minutes
- flex not installed (required by CMake find_package)5 minutes
- libyaml-dev not installed (required by FLB_CONFIG_YAML)5 minutes
- flb-it-network fails due to IPv6 disabled in container (nosuid noexec container)
- Install time
- 30 minutes
- Cold machine to finish
- 36 minutes
- Errors hit and fixed
- 5 hit, 4 fixed with no human help
- How the result was proved
- cmake --build build -j8 succeeded (exit 0). ctest --test-dir build -R flb-it- --output-on-failure: 96/97 passed, 1 failed (flb-it-network, IPv6 disabled in container). ./build/bin/fluent-bit --version returned 'Fluent Bit v5.1.3'. ./build/bin/fluent-bit -i cpu -o stdout -f 1 ran with live output.
- Model tokens used
- 171,760
- Exact commit tested
- 046accf6aded
- 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.
**Build**: cmake built successfully with flex, bison, libyaml all compiled from source (no root acc… **Binary**: `/work/repo/build/bin/fluent-bit --version` reports `Fluent Bit v5.1.3`. The `-i cpu -o… **Tests**: 96 of 97 internal `flb-it-*` tests pass. The single failure is `flb-it-network` which te… **Runtime tests** (216 tests) exist but were not run — they take several minutes and require simula… 2026-09-28T06:20:24.392568Z ERROR codex_core::session: failed to record rollout items: thread 01a0e… tokens used 171,760 Here are the results of my full verification: **Build**: cmake built successfully with flex, bison, libyaml all compiled from source (no root acc… **Binary**: `/work/repo/build/bin/fluent-bit --version` reports `Fluent Bit v5.1.3`. The `-i cpu -o… **Tests**: 96 of 97 internal `flb-it-*` tests pass. The single failure is `flb-it-network` which te… **Runtime tests** (216 tests) exist but were not run — they take several minutes and require simula…
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 30 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Hit 5 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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)
ccloudnativedata-collectorfluent-bitfluentdforwarderlogginglogsmetricsopentelemetryprometheussql-queriesstream-processingtraces
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/fluent-bit)Questions
- Does fluent-bit run?
- Yes. fluent-bit runs. Argusic installed and launched it on a clean machine in 30 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test fluent-bit?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 046accf6aded. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test fluent-bit?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does fluent-bit take to install?
- 30 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 fluent-bit need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing fluent-bit?
- 5 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for fluent-bit?
- 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.