|
1 | 1 | # What's new in Fluent Bit v5.0 |
2 | 2 |
|
3 | | -Fluent Bit `v5.0` adds new inputs and processors, expands authentication and TLS options, and standardizes configuration for HTTP-based plugins. This page gives a quick user-focused overview of the main changes since Fluent Bit `v4.2`. |
| 3 | +Fluent Bit `v5.0` adds new inputs and processors, expands authentication and TLS options, and standardizes configuration for HTTP-based plugins. It also delivers an important round of performance and scalability work, especially for pipelines that ingest logs, metrics, and traces through HTTP-based protocols. This page gives a quick user-focused overview of the main changes since Fluent Bit `v4.2`. |
4 | 4 |
|
5 | 5 | For migration-impacting changes, see [Upgrade notes](upgrade-notes.md). |
6 | 6 |
|
| 7 | +## Performance and scalability |
| 8 | + |
| 9 | +### Unified processing and delivery model |
| 10 | + |
| 11 | +Fluent Bit `v5.0` continues the move toward a more unified runtime for logs, metrics, and traces. In practice, this means the same core engine improvements benefit more of the pipeline, instead of individual signal paths evolving separately. |
| 12 | + |
| 13 | +For end users, the result is a more consistent behavior across telemetry types and a better base for high-throughput pipelines that mix logs, metrics, and traces in the same deployment. |
| 14 | + |
| 15 | +### Refactored HTTP stack |
| 16 | + |
| 17 | +One of the most important `v5.0` changes is the refactoring of the HTTP listener stack used by several input plugins. Fluent Bit now uses a shared HTTP server implementation across the major HTTP-based receivers instead of maintaining separate code paths. |
| 18 | + |
| 19 | +This work improves: |
| 20 | + |
| 21 | +- concurrency through shared listener worker support |
| 22 | +- consistency of request handling across HTTP-based inputs |
| 23 | +- buffer enforcement and connection handling |
| 24 | +- maintainability, which reduces drift between plugin implementations |
| 25 | + |
| 26 | +The biggest user-facing beneficiaries are: |
| 27 | + |
| 28 | +- [HTTP input](../pipeline/inputs/http.md) |
| 29 | +- [Splunk input](../pipeline/inputs/splunk.md) |
| 30 | +- [Elasticsearch input](../pipeline/inputs/elasticsearch.md) |
| 31 | +- [OpenTelemetry input](../pipeline/inputs/opentelemetry.md) |
| 32 | +- [Prometheus remote write input](../pipeline/inputs/prometheus-remote-write.md) |
| 33 | + |
| 34 | +If you run large HTTP or OTLP ingestion workloads, `v5.0` is not only a feature release. It is also a meaningful runtime improvement. |
| 35 | + |
7 | 36 | ## Configuration and operations |
8 | 37 |
|
9 | 38 | ### Shared HTTP listener settings |
|
0 commit comments