Meet Fluent Bit 5.2.

Faster telemetry. Typed scripting. More resilient delivery.

Your quick guide to the release, the demos, and the people building it.

Try Fluent Bit Studio Find us at Kiosk P-12A

The release at a glance

Small agent. Bigger possibilities.

Collect, process, and route logs, metrics, and traces with Fluent Bit 5.2.

Typed scripting for all three signals

Fluent Typed Scripting (FTS) brings Lua policies to logs, metrics, and traces. Redact sensitive fields, normalize telemetry, and reduce noise while preserving typed values and OpenTelemetry context. Explore FTS →

Faster OpenTelemetry pipelines

Native processing improvements accelerate log ingestion and transformations. Compatible Content Modifier chains apply multiple edits in one pass. Inspect the benchmarks →

Delivery that responds to busy backends

HTTP, OpenTelemetry, Elasticsearch, and OpenSearch outputs honor supported throttling responses and retry-delay hints. Waiting through a cooldown does not consume retry attempts.

More efficient buffering

Filesystem buffering uses disk more efficiently for low-volume streams, while large log buffers are processed in bounded windows.

System logs, ready for OpenTelemetry

The new journald_otel processor maps journal records into OTel logs, including severity, host, and process information.

Fluent Bit in the browser

An experimental WebAssembly browser SDK brings configuration, JSON log ingestion, and engine lifecycle controls to browser applications. Try Fluent Bit Studio →

Read the complete 5.2 release notes

More throughput. Less CPU per log.

Performance you can inspect.

1.50Mrecords per second

7.2×throughput vs 5.1

69.6%less CPU time per million logs vs 5.1

One measured workload: OTLP/HTTP JSON, adding one log attribute with native Content Modifier, memory buffering, and null output. 30M records per run, five runs. CPU time: 8.07 → 2.45 seconds per million records. Results depend on workload and hardware.

Explore results & methodology

Get hands-on

Bring a policy. Try it in Studio.

Write and test FTS Lua policies on sample logs, and explore Fluent Bit routing in your browser.

Open Fluent Bit Studio

FTS / redact a sensitive field

local fb = require("fluentbit")

function process(log)
  fb.redact(log.body, {"password"})
end

Hear from the maintainer

Join us on Wednesday.

All times are Salt Lake City local time: MST (UTC−7).

Wednesday · Maintainer Track

Engineering High-Performance Telemetry Pipelines: Lessons from Fluent Bit

Profiling, optimization, and the tradeoffs behind Fluent Bit’s latest performance work.

Eduardo Silva
Wednesday, November 11 · 11:00–11:30 AM
Salt Palace · Level 2 · 250 A-C

View Wednesday’s session

Also on the program · Monday lightning talk

Fluent Bit: The Evolution of High-Performance Telemetry Pipelines

Eduardo Silva
Monday, November 9 · 11:24–11:29 AM
Hyatt Regency · Level 4 · Regency Ballroom B-D

View lightning talk

Check the official program for the latest times and rooms.

Meet the Fluent Bit community

Stop by the Fluent Bit Kiosk.

P-12A

See Fluent Bit 5.2 and Studio, bring your pipeline questions, and talk with the people behind the project.

Project Pavilion · Cosmic Canyon Zone
Salt Palace · Level 1 · Solutions Showcase · Hall 5

Visit us Wednesday, November 11

Morning10:30 AM–1:25 PM Afternoon1:55–5:00 PM

MST (UTC−7). Kiosk hours follow the official Project Pavilion schedule.

Keep exploring.

5.2 release notes Performance benchmarks Fluent Bit Studio Get started with Fluent Bit