Thiago Gomes
07/12/2025, 5:40 AMPat
07/12/2025, 11:53 AMThiago Gomes
07/13/2025, 11:17 PMforward protocol (Fluent Bit → Fluent Bit) to AWS, but unfortunately, it's still not working as expected. On the other hand, the logs are being successfully sent via Fluent Bit to Fluentd. I can confirm that all expected servers appear on the Fluentd instance in AWS.
Below is the current topology and configuration setup I’m using:
Fluent Bit Agents] [proxy aggregator] [AWS NLB] [EC2]
------------------------ non-TLS -----> Fluent Bit ----------- TLS -----> AWS NLB -----> Fluent Bit (Metrics)
fluent-bit 1 \
fluent-bit 2 \-> Fluentd (Logs) – OK
fluent-bit 3
fluent-bit 4
fluent-bit 5
fluent-bit 6
The Fluent Bit instance running in AWS (receiving metrics from the proxy server) behaves inconsistently, sometimes it receives metrics from some agents, but others randomly drop off and never reconnect unless restarted.Thiago Gomes
07/13/2025, 11:25 PMThiago Gomes
07/15/2025, 4:53 AMin_forward plugin in Fluent Bit.Thiago Gomes
07/21/2025, 9:15 PMPat
07/22/2025, 9:06 AM