You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Requirement - what kind of business use case are you trying to solve?
We are implementing a custom gRPC-based storage plugin as per this doc.
Problem - what in Jaeger blocks you from solving the requirement?
The data that our plugin puts into Span tags can include big integer IDs (uint64). Since many languages don't deal with large integers in JSON nicely all such IDs are stringified. However even in string form Jaeger tries to interpret these tags as integers which results in rounding issues.
Proposal - what do you suggest to solve the problem or improve the existing situation?
A simplest way to reproduce this issue is to modify in-memory gRPC plugin to return following fake span:
Requirement - what kind of business use case are you trying to solve?
We are implementing a custom gRPC-based storage plugin as per this doc.
Problem - what in Jaeger blocks you from solving the requirement?
The data that our plugin puts into Span tags can include big integer IDs (uint64). Since many languages don't deal with large integers in JSON nicely all such IDs are stringified. However even in string form Jaeger tries to interpret these tags as integers which results in rounding issues.
Proposal - what do you suggest to solve the problem or improve the existing situation?
A simplest way to reproduce this issue is to modify in-memory gRPC plugin to return following fake span:
The key line is:
Searching for a span in Jaeger UI shows that this tag has been converted to integer with loss of precision:
Modifying the value to contain non-numeric characters results in correct string type:
Any open questions to address
The text was updated successfully, but these errors were encountered: