Upgrade fluent-bit (Linux 5.0.4, Windows 5.0.3)#1671
Merged
Conversation
- Linux: azcu-fluent-bit 4.0.14 -> 5.0.4 (spec already published in dalec-build-defs) - Windows: fluent-bit 4.0.3 -> 5.0.3 (latest available zip on packages.fluentbit.io) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
Contributor
|
Please share the resource usage as well. |
Contributor
Author
// see metrics are flowing
|
rashmichandrashekar
approved these changes
May 14, 2026
Contributor
Author
updated in the pr |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Upgrades fluent-bit to the latest available versions on each platform.
kubernetes/linux/setup.shazcu-fluent-bit-4.0.14azcu-fluent-bit-5.0.4kubernetes/windows/setup.ps1fluent-bit-4.0.3-win64.zipfluent-bit-5.0.3-win64.zipNotes
azcu-fluent-bit-5.0.4spec is already published in Azure/dalec-build-defs#7471, so no companion PR is needed there.https://packages.fluentbit.io/windows/. Upstream 5.0.4 has been released but the Windows zip has not been pushed yet.fluent-bit 4.0.14 → 5.0.x Upgrade — Validation Summary
PR: #1671 (
zanejohnson-azure/upgrade-fluent-bit)Changes:
kubernetes/linux/setup.sh→azcu-fluent-bit-5.0.4kubernetes/windows/setup.ps1→fluent-bit-5.0.3-win64.zip(5.0.4 not yet published upstream — will bump when available)Verdict: ✅ No regressions. Safe to merge once Windows 5.0.4 lands.
How it was validated
cpu and memory usage after and before
First half is from new fluent-bit and second half is from current fluent-bit version.
linux
both cpu and memory usage actually dropped in new version.

windows
cpu slightly dropped and memory usage slightly increased in new fluent-bit version. There was a transient memory jump for a couple of minutes in new fluent-bit version, but dropped quickly to a stable level.

A/B backdoor deployment on AKS cluster
zane-ama-logs-helm-test(LA workspace222e72f7-1ad8-4e28-b2a9-07d046eedef4):ciprod:3.3.0(current prod, fluent-bit 4.0.14)cidev:3.3.0-6-g1d77401ab-20260506045747(this PR, fluent-bit 5.0.4 Linux)Data-volume parity (1-min bins, 5-min window)
azsecpack-azl3-image(Azure Security Linux DaemonSet) snapshotsPer-container investigation confirmed the small deltas are unrelated cluster churn (azsecpack), not the ama-logs code change.
Functional smoke tests
kubectl rollout restart ds/ama-logsclean, 4/4 pods ReadyMultiline stack-trace grouping (the highest-risk 5.x area)
fluent-bit 5.x rewrote
in_emitterand the multiline buffering path. ama-logs gates multiline behind a customer opt-in (#${MultilineEnabled}token influent-bit.confstripped byfluent-bit-conf-customizer.rbwhenenable_multiline_logs.enabled = "true"). Tested explicitly:Method: Deployed a busybox pod (
multiline-emitter) that prints a 7-line Java NPE +Caused by:chain every 30 s, taggediter-N. CapturedContainerLogV2rows before (multiline OFF) and after (configmap patch enabling multiline forjava).\n-terminated line)Sample AFTER row (
iter-19LogMessage):Result: Multiline grouping works as documented on 5.0.4. No partial traces, no dropped continuation lines, no duplicate emissions.