We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Current Jaeger Thrift exporter implementation maps service_name from resource attributes into Jaeger process. The rest of the resource attributes also need to be mapped to the Jaeger Process as mentioned in specs: https://github.com/open-telemetry/opentelemetry-specification/blob/v1.0.0/specification/trace/sdk_exporters/jaeger.md#resource
This is how it is handled by otel-go implementation: https://github.com/open-telemetry/opentelemetry-go/blob/d3b1280863f421bba9656543296b71c133f1ba13/exporters/trace/jaeger/jaeger.go#L346
The text was updated successfully, but these errors were encountered:
@lalitb Can you assign this to me?
Sorry, something went wrong.
@anshulkumar19 - Do you want me to pick this up, as we need to fix this for GA.
Sorry @lalitb for coming late on this, please pick this up as needed for GA and I am little bit occupied with other things.
@anshulkumar19 no problem. I'll take it.
ThomsonTan
Successfully merging a pull request may close this issue.
Current Jaeger Thrift exporter implementation maps service_name from resource attributes into Jaeger process. The rest of the resource attributes also need to be mapped to the Jaeger Process as mentioned in specs:
https://github.com/open-telemetry/opentelemetry-specification/blob/v1.0.0/specification/trace/sdk_exporters/jaeger.md#resource
This is how it is handled by otel-go implementation: https://github.com/open-telemetry/opentelemetry-go/blob/d3b1280863f421bba9656543296b71c133f1ba13/exporters/trace/jaeger/jaeger.go#L346
The text was updated successfully, but these errors were encountered: