This repository has been archived by the owner on Sep 13, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 131
Large spans not sending correctly #242
Labels
Comments
I think the best solution would be to support HTTP sender (#170) which would have much higher limits on the span size. Other things that could be done are:
|
Related you can use flushIntervalMs to flush more frequently that would reduce the size . |
Thanks @claudio-viola |
Iuriy-Budnikov
pushed a commit
to agile-pm/jaeger-client-node
that referenced
this issue
Sep 25, 2021
closes jaegertracing#242 Signed-off-by: Olivier Albertini <olivier.albertini@montreal.ca>
Iuriy-Budnikov
pushed a commit
to agile-pm/jaeger-client-node
that referenced
this issue
Sep 25, 2021
closes jaegertracing#242 Signed-off-by: Olivier Albertini <olivier.albertini@montreal.ca>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello!
We have problems with large spans, when we call span.log with data greater than UDP_PACKET_MAX_LENGTH, these spans do not reach correctly and are not visible later in the UI.
Does jaeger can not send (or split them to several packets) large spans?
The text was updated successfully, but these errors were encountered: