-
Notifications
You must be signed in to change notification settings - Fork 63
receiver/jaeger: translation of Jaeger agent tags are lost #605
Comments
@flands per jaegertracing/jaeger#833 (comment) Jaeger agent is only capable to add tags to gRPC. It seems the case that you described. |
Can you try the same against OpenTelemetry service that has a Jaeger gRPC receiver? |
I opened census-instrumentation/opencensus-java#1959 but was closed as a duplicate of this one. But I am not completely sure what the recommendation is. Reference to OpenCensus Service deployment architecture: https://github.com/census-instrumentation/opencensus-service#user-content-deploy I have jaeger traces -> OpenCensus Agent -> OpenCensus Collector -> Stackdriver and looks like the (application) tags and metadata gets dropped or at least I do not see them in Stackdriver console. Would the Stackdriver exporter export tags and metadata from jaeger traces? Or are they getting dropped even before Stackdriver exporter? |
I had ocagent:
occollector:
But the ocagent was sending to occollector via opencensus receiver
I tried changing to ocagent:
occollector:
And the ocagent sending to occollector via jaeger receiver
Now I do not get the traces from occollector sent to stackdriver any more |
This repository is now archived, and is succeeded by https://github.com/open-telemetry/opentelemetry-collector. |
Configure an application to send Jaeger to the Jaeger agent. Configure the Jaeger agent to add tags to the data it is sending out. Configure the Jaeger agent to send tchannel to the OC collector. Have the OC collector export in OC to a backend.
Expected: Jaeger agent tags are seen on spans
Actual: Jaeger agent tags are NOT seen on spans.
The text was updated successfully, but these errors were encountered: