Skip to content
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

FluentBit - Sending queue is full when trying to send logs. #1786

Open
simlarsen opened this issue Jan 9, 2025 · 9 comments
Open

FluentBit - Sending queue is full when trying to send logs. #1786

simlarsen opened this issue Jan 9, 2025 · 9 comments
Labels
bug Something isn't working high priority High priority issue

Comments

@simlarsen
Copy link
Contributor

����sending queue is full
[2025/01/08 20:13:48] [ warn] [engine] failed to flush chunk '1-1736367227.589268651.flb', retry in 11 seconds: task_id=10, input=tail.0 > output=opentelemetry.0 (out_id=0)
[2025/01/08 20:13:49] [ info] [output:opentelemetry:opentelemetry.0] oneuptime.com:443, HTTP status=200
@simlarsen simlarsen added the bug Something isn't working label Jan 9, 2025
@edgarrmondragon
Copy link

fwiw the error does seem to be coming from the OTEL collector used by OneUptime: https://github.com/open-telemetry/opentelemetry-collector/blob/12b0369f16c0f7c5e45832dc05bfc2960975cd50/exporter/exporterqueue/queue.go#L18

@simlarsen
Copy link
Contributor Author

@edgarrmondragon Can you please look into this. This should now be fixed. Please feel free to reopen this issue if you think this is still not fixed.

@edgarrmondragon
Copy link

Hey @simlarsen, I think we're still experiencing this:

[2025/01/14 12:56:27] [error] [output:opentelemetry:opentelemetry.0] oneuptime.com:443, HTTP status=503
����sending queue is full
[2025/01/14 12:56:27] [ warn] [engine] failed to flush chunk '1-1736859386.398660857.flb', retry in 7 seconds: task_id=1, input=tail.0 > output=opentelemetry.0 (out_id=0)
[2025/01/14 12:56:28] [ info] [output:opentelemetry:opentelemetry.0] oneuptime.com:443, HTTP status=200

@simlarsen simlarsen reopened this Jan 14, 2025
@simlarsen
Copy link
Contributor Author

@edgarrmondragon Looking into this.

@simlarsen simlarsen added the high priority High priority issue label Jan 14, 2025
@simlarsen
Copy link
Contributor Author

Can you please let me know if this is fixed for you now? If not let me know and I can re-open this issue.

@edgarrmondragon
Copy link

Thank you @simlarsen, we're currently monitoring and I'll let you know if the error no longer rears its heads in the coming days.

(So far things are looking good 🎉)

@edgarrmondragon
Copy link

@simlarsen we're still occasionally seeing the 503s and sending queue is full errors:

[2025/01/17 16:21:06] [error] [output:opentelemetry:opentelemetry.0] oneuptime.com:443, HTTP status=503
��sending queue is full
[2025/01/17 16:21:06] [ warn] [engine] failed to flush chunk '1-1737130865.520098411.flb', retry in 10 seconds: task_id=0, input=tail.0 > output=opentelemetry.0 (out_id=0)
[2025/01/17 16:21:07] [error] [output:opentelemetry:opentelemetry.0] oneuptime.com:443, HTTP status=503
��sending queue is full
[2025/01/17 16:21:07] [ warn] [engine] failed to flush chunk '1-1737130866.527146668.flb', retry in 8 seconds: task_id=1, input=tail.0 > output=opentelemetry.0 (out_id=0)
[2025/01/17 16:21:08] [ info] [output:opentelemetry:opentelemetry.0] oneuptime.com:443, HTTP status=200


[2025/01/17 16:21:09] [error] [output:opentelemetry:opentelemetry.0] oneuptime.com:443, HTTP status=503
��sending queue is full
[2025/01/17 16:21:09] [ warn] [engine] failed to flush chunk '1-1737130868.518212564.flb', retry in 9 seconds: task_id=2, input=tail.0 > output=opentelemetry.0 (out_id=0

@simlarsen
Copy link
Contributor Author

@edgarrmondragon got it! Let me look into this and investigate.

@simlarsen simlarsen reopened this Jan 20, 2025
@simlarsen
Copy link
Contributor Author

@edgarrmondragon workign on this today / tomorrow. Will have an update soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working high priority High priority issue
Projects
None yet
Development

No branches or pull requests

2 participants