Skip to content
New issue

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

[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
Labels

Comments

@vishal-singh3
Copy link

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

  1. Create a spring boot project for tracing and observability.
  2. Basic setup for Jaeger tracing.
  3. Send a post /get request to one of the Spring controller.
  4. Throw the exception from the said Spring controller.
  5. 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

@yurishkuro
Copy link
Member

yurishkuro commented Dec 6, 2024

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.

@vishal-singh3
Copy link
Author

Actual :

Image

Expected :

Image

Attached zipkin json payload for further testing zipkin_payload.txt

@yurishkuro
Copy link
Member

zipkin_payload.txt this is not in zipkin format. We need the original payload exported by your application.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants