We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
����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
The text was updated successfully, but these errors were encountered:
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
Sorry, something went wrong.
@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.
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
@edgarrmondragon Looking into this.
No branches or pull requests
The text was updated successfully, but these errors were encountered: