LoginSign Up
← Back to all sparks
F

Fluent Bit

ANALYTICS
Velocity5.0

Lightweight telemetry and log processor and forwarder

fluentbit.io ↗

Fluent Bit keeps two lines alive while the 5.x branch quietly opens 5.1.

observabilitylog-pipelinememory-safetybackportswindowsrelease-tagging
◆Current state
Three release lines are visible at once. The 4.2 branch takes backported fixes — Stackdriver payload over-reads, Avro empty-map handling, Windows event-log enrichment. The 5.0 line carries the forward work. And a 5.1 line has appeared with two tags whose titles are raw commit messages about test changes, which is what this repository produces when a tag is cut off a routine commit rather than a prepared release.
◆Where it's heading
The engineering emphasis on the maintained branches is memory safety and protocol correctness in the input and output plugins: use-after-free in in_forward, over-reads in out_stackdriver, endian-safe gzip magic reads, oauth2 token parsing hardening. That is the profile of a project whose failure mode is a crash in someone else's log pipeline, and it is being worked systematically rather than opportunistically.
◆Prediction
Expect the 4.2 backport stream to continue at roughly monthly cadence and the 5.1 line to keep accumulating commit-titled tags until a prepared announcement release appears with real notes.

◆Recent moves

  1. 4d ago

    5.1.1 tagged off a storage-limit test commit

    Another 5.1 tag whose entire content is a test change keeping a chunk size signed until its error result is checked. Tag noise rather than a release — the same pattern as 5.1.0.

    View source ↗
  2. 13d ago

    5.1.0 tagged with only an integration-test commit

    The 5.1 line opens with a tag carrying a single integration test for split HTTP/1 protocol detection. It marks a branch existing, not a release shipping.

    View source ↗
  3. 15d ago

    Fluent Bit 4.2.8

    A small 4.2 backport round: Windows event-log key-value enrichment, a Stackdriver payload over-read and null-safety fix, and Avro empty-map handling in out_kafka. Maintenance-branch upkeep.

    View source ↗
  4. 1mo ago

    Fluent Bit 4.2.7

    A substantial backport round fixing a 100% CPU hang and connection-teardown use-after-free in in_forward, aligning the secure forward handshake with the protocol spec, and making the gzip streaming decompressor endian-safe. The clearest expression of the memory-safety arc on the maintained branch.

    View source ↗
  5. 1mo ago

    Fluent Bit 5.0.9

    Mostly workflow and dependency churn, with one real addition: user-defined performance counters via PDH in the Windows exporter metrics input. Forward-line work while 4.2 takes backports.

    View source ↗
  6. 1mo ago

    Fluent Bit 4.2.6

    IANA time zone support for native timestamps and Windows/IANA tzinfo conversion, plus multiple Stackdriver memory leaks and oauth2 token-refresh parsing hardened. Timestamp correctness and memory safety in the same round.

    View source ↗