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
[Bug]: From Jaeger version 1.53.0 'error.message' tag value is missing, 'error' tag contains both true value and error message. This makes it difficult to retrieve the tags proper value.
#6317
Open
vishal-singh3 opened this issue
Dec 6, 2024
· 3 comments
Until version Jaeger 1.52.0 the error and error.message tag display proper values.
since version Jaeger 1.53.0 error tag has both values of true and error message; error.message tag is diappeared.
Steps to reproduce
Create a spring boot project for tracing and observability.
Basic setup for Jaeger tracing.
Send a post /get request to one of the Spring controller.
Throw the exception from the said Spring controller.
Check the span and tags for the failed request and look for error and error.message tag.
Expected behavior
Like previous versions error and error.message tag must be properly displayed in the span.
Relevant log output
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
The text was updated successfully, but these errors were encountered:
I cannot use these "Steps to reproduce", they are too complicated and irrelevant to the problem. Please upload a zipkin JSON payload, then we can test.
The change is most likely caused by switching to Zipkin receiver from OTEL #5045. It has been marked as a breaking change in the release notes.
What happened?
Using zipkin collector for Jaeger Tracing.
Until version Jaeger 1.52.0 the error and error.message tag display proper values.
since version Jaeger 1.53.0 error tag has both values of true and error message; error.message tag is diappeared.
Steps to reproduce
Expected behavior
Like previous versions error and error.message tag must be properly displayed in the span.
Relevant log output
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
The text was updated successfully, but these errors were encountered: