The Fluent community announced the release of Fluent Bit v4.2, the latest version of the open-source telemetry processor.
Coinciding with its 10th anniversary, Fluent Bit continues to set the standard for lightweight, high-performance, and vendor-neutral observability, trusted by enterprises worldwide.
Fluent Bit has grown from a simple log collector to a comprehensive, multi-signal telemetry agent, with adoption spanning tens of billions of downloads and integration across major Kubernetes distributions from AWS, Google Cloud, Microsoft Azure, and Oracle. Nearly a quarter of Fortune 100 companies have adopted or contributed to Fluent Bit, underscoring its position as a cornerstone of the cloud native ecosystem.
Key Release Features Include:
- Flexible Telemetry Routing: The new Telemetry Router enables content-aware routing based on record metadata, attributes, or tags, allowing users to define dynamic data flows without relying on traditional tag-based matching. The new complementary routing metrics provide per-path visibility of record and byte throughput across inputs and outputs.
- Performance Breakthroughs: Pipeline optimizations enable twice the speed of JSON generation through SIMD-accelerated writing, and provide faster and more efficient Trace Sampling with reduced CPU and memory usage.
- Reliability and Security: The new Supervisor Mode continuously monitors and restarts child processes to ensure consistent uptime. The independent Hot Reload Watchdog validates and protects configuration updates at runtime. Lastly, the enhanced TLS session handling with ALPN support strengthens secure connectivity and resilience.
- Expanded Data Outputs and OpenTelemetry Enhancements: The Amazon S3 output now supports Parquet format with Apache Arrow and ZSTD compression, while the OpenTelemetry output introduces updated protocol support and AWS SigV4 authentication.
- Next-Level Observability: The new GPU metrics collector (AMD) and Prometheus textfile collector for .prom files expand system-level introspection and monitoring flexibility.
- Broader Platform Support: Now supporting Debian Trixie, Rocky/AlmaLinux 10, CentOS Stream 10, the latest openSUSE release, and improved Windows Certstore compatibility.
“With Fluent Bit v4.2, we’re raising the bar for performance, reliability, and extensibility while staying true to our founding principles of lightweight and vendor-neutral design,” said Eduardo Silva Pereira, Project Creator and Maintainer, Fluent Bit. “As we celebrate a decade of community-driven innovation, this release reflects both how far we’ve come and how prepared we are for the next decade of observability challenges.”
Since its creation in 2015, Fluent Bit has grown into the most widely used telemetry agent in the cloud native ecosystem, celebrated for its efficiency, scalability, and open governance under the Cloud Native Computing Foundation (CNCF). This anniversary highlights not only a decade of technical progress, but also a thriving, collaborative global community.
The Fluent community recently proposed restructuring Fluentd and Fluent Bit under a unified Fluent organization at CNCF. This change will:
- Create a shared governance model while preserving project independence.
- Enable future growth of new observability projects under the Fluent umbrella.
- Maintain vendor neutrality with no changes to licenses, names, or day-to-day contributions.
Community feedback and voting will be conducted under CNCF guidance to ensure transparency and inclusivity.
The Latest
In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...
AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.