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 15 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Fluent Bit v5.1.3 builds from source with all features enabled, runs a cpu→stdout pipeline producing valid JSON metrics, and passes both its internal C test suites and the in_http Python integration tests.

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 98 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
98 / 100
cost of the verifying run
$0.18 (measured)
recorded runs
2
last tested
stars
8,191
forks
2,038
open issues
857
watchers
104
size
160 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 fluent-bit, 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.

  • System packages flex, bison, libyaml-dev not installed10 minutes
  • Config cmake error: YAML dev not found5 minutes
  • Config cmake error: Record Accessor requires flex/bison
  • Config cmake error: Stream Processor requires flex/bison
  • Build error: in_prometheus_textfile missing cmt_decode_prometheus symbols
Install time
15 minutes
Cold machine to finish
49 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
`/work/repo/build/bin/fluent-bit -i cpu -o stdout -f 1` produced metrics output; `FLUENT_BIT_BINARY=/work/repo/build/bin/fluent-bit .venv/bin/python -m pytest scenarios/in_http/tests/ -q` returned 8 passed; individual flb-it-* test binaries all passed
Model tokens used
609,024
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.

609,024
Now let me compile the final results and report.
Here's my summary of everything I did:
## Assessment
**Build**: CMake configured and built Fulent Bit v5.1.3 from source successfully. Needed 3 locally-…
**Launch**: The binary runs and produces output. Tested with `-i cpu -o stdout`.
**Tests**: All toggle erted internal C test suites pass. The Python integration test for `in_http` …
**Errors encountered**:
1. flex & bison missing → built from source
2. libyaml missing → built from source
3. `in_prometheus_textfile`, `in_prometheus_scrape`, `in_node_exporter_metrics` all depend on the p…
4. `CMT_PROMETHEUS_TEXT_DECODER` was initially off but turned back on after we built flex/bison

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 15 minutes, faster than the median of the 6 comparable projects Argusic has measured.
  • 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.

Of the 7 c projects Argusic has installed and timed, fluent-bit was the 3rd fastest to reach a running state, and 6 of 7 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.18
Argusic Runner1/3Runs96.000.13

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.

[![Tested by Argusic](https://argusic.com/badge/fluent-bit.svg)](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 15 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. 2 attempts are 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.18: 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?
15 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 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does fluent-bit compare with the alternatives?
Of the 7 c projects Argusic has installed and timed, fluent-bit was the 3rd fastest to reach a running state, and 6 of 7 reached one at all.
Where is the evidence for fluent-bit?
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