-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fluent-bit crashes when handling envoy empty spans #9391
Comments
fixed in #9430 |
Regression: in 3.2.6 with Envoy 1.30.16 |
Repro for below
|
hi @carlos4ndre |
@lecaros Thank you for your help. I've tested with the latest version of fluent-bit 3.2.8 but unfortunately still not receiving any traces on the otel collector, all seems to point out that traces are being dropped by fluent-bit. Fluent-bit logs:
OTel collector logs:
docker-compose.yaml
fluent-bit.conf
otel-collector.yaml
envoy.yaml
Run Other notes, also tried with the latest version of envoy (v1.33.0) but achieved the same results. |
Hi @carlos4ndre, |
@lecaros Thanks! that was the issue, setting
Traces are properly processed and forwarded by fluent-bit:
Traces are successfully delivered to the otel collector:
However it is important to note that I've had to downgrade fluent-bit to |
Closing this issue since the bug initially reported has been fixed. |
Bug Report
Describe the bug
I’m having an issue using fluent-bit (3.1.7) when processing spans sent by Envoy.
The flow is like this: Envoy -> fluent-bit -> OTel collector
From what I can see in the logs, Envoy is sending some periodic data (every 10s) but with empty spans, probably some sort of health check and causes fluent-bit to crash.
Not sure if this is a well known issue. Envoy is configured to send traces over gRPC.
To Reproduce
fluent-bit.conf
otel-collector.yaml
envoy.yaml
event_type
input to show thatopentelemetry
output works fine with normal span payloads:Expected behaviour
Fluent-bit does not crash when receiving empty spans from Envoy, or allow a way to filter them.
Your Environment
The text was updated successfully, but these errors were encountered: