Skip to content
This repository has been archived by the owner on Nov 7, 2022. It is now read-only.

receiver/jaeger: translation of Jaeger agent tags are lost #605

Closed
flands opened this issue Jul 12, 2019 · 5 comments
Closed

receiver/jaeger: translation of Jaeger agent tags are lost #605

flands opened this issue Jul 12, 2019 · 5 comments

Comments

@flands
Copy link
Contributor

flands commented Jul 12, 2019

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.

@pjanotti
Copy link

@flands per jaegertracing/jaeger#833 (comment) Jaeger agent is only capable to add tags to gRPC. It seems the case that you described.

@pjanotti
Copy link

pjanotti commented Aug 9, 2019

Can you try the same against OpenTelemetry service that has a Jaeger gRPC receiver?

@part-time-githubber
Copy link

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?

@part-time-githubber
Copy link

part-time-githubber commented Aug 15, 2019

I had

ocagent:

    receivers:
        jaeger:
            collector_http_port: {{ .Values.jaeger_thrift_http_port }}

occollector:

    receivers:
        jaeger:
            jaeger-thrift-http-port: {{ .Values.jaeger_thrift_http_port }}

But the ocagent was sending to occollector via opencensus receiver

 exporters:
        opencensus:
            endpoint: "{{ include "opencensus-service.fullname" . }}-collector:{{ .Values.opencensus_port }}"

I tried changing to

ocagent:

    receivers:
        jaeger:
            collector_http_port: {{ .Values.jaeger_thrift_http_port }}

occollector:

    receivers:
        jaeger:
            jaeger-thrift-tchannel-port: {{ .Values.jaeger_thrift_tchannel_port }}

And the ocagent sending to occollector via jaeger receiver

 exporters:
        opencensus:
            endpoint: "{{ include "opencensus-service.fullname" . }}-collector:{{ .Values.jaeger_thrift_tchannel_port }}"

Now I do not get the traces from occollector sent to stackdriver any more

@dashpole
Copy link
Contributor

dashpole commented Nov 7, 2022

This repository is now archived, and is succeeded by https://github.com/open-telemetry/opentelemetry-collector.

@dashpole dashpole closed this as completed Nov 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants