More expressive error for EMSGSIZE from Jaeger reporter #89
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We observe around 22k of these errors per day in production and don't have any information to investigate further. By adding the span name as well as some tag and log information, we should be able to pin down which trace spans are excessively large and limit those in our code.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We observe around 22k
EMSGSIZEerrors per day in production and don't have any information to investigate further. By adding the span name as well as some tag and log information, we should be able to pin down which trace spans are excessively large and limit those in our code.This error can only occur with the Jaeger UDP transport, since OTLP uses gRPC which doesn't limit message size.