Fluent Bit
Lightweight telemetry and log processor and forwarder
Fluent Bit spends October bounding what its inputs will accept.
◆Recent moves
- 12d ago
5.1.5 bounds Lua reads and mitigates CRLF header injection
5.1.5 is the broadest of the hardening releases: bounded Lua reads, forward and collectd decoding fixes, CRLF injection mitigated in the HTTP client and Loki output, and JWTs concealed from debug logs. It also adds Chronicle API support and PATCH on out_http.
View source ↗ - 17d ago
5.1.4 limits OTLP decompression and msgpack unpacking
Continues the input-safety run by limiting OTLP gRPC decompression, budgeting msgpack objects and bounding Kubernetes filter tags. It also enforces the multiline buffer limit for EQ and ENDSWITH types.
View source ↗ - 24d ago
5.0.11: winevtlog crash fix and Kafka packaging backports
A small backport to the 5.0 line: a Windows event log crash fix and packaging changes that enable Kafka plugins on CentOS Stream 9 and 10.
View source ↗ - 1mo ago
5.1.3: Kafka protobuf schemas, TLS CRL files, S3 crash fix
A mixed release that starts the shift to input safety while still adding capability: protobuf for the Kafka schema registry, tls.crl_file, an ArvanCloud output and a metric age filter, plus out_s3 heap corruption and GCS crash fixes.
View source ↗ - 1mo ago
Fluent Bit 5.1.2: GCS Parquet compression and WIF support
5.1.2 is the largest 5.1.x drop so far, adding Parquet compression and Workload Identity Federation to the GCS output, namespace-scoped systemd capture, Kubernetes namespace exclusion in the filter, and a built-in JSON multiline parser — extending the 5.x capability surface across cloud storage and Kubernetes-native use cases. The macOS stat and thermal metrics rounding out the node exporter fit the same pattern of closing platform gaps rather than introducing new directions.
View source ↗ - 1mo ago
Fluent Bit 5.0.10: maintenance backports
5.0.10 is a backport-only release, cherry-picking TLS retry, Windows event log enrichment, Avro/Kafka, and a batch of maintenance fixes from 5.1 onto the stable 5.0 branch. No net-new capability — this is the stable channel getting the fixes that landed in 5.1 upstream.
View source ↗