search

envoyproxy / envoy

Cloud-native high-performance edge/middle/service proxy
https://www.envoyproxy.io
Apache License 2.0
24.67k stars 4.75k forks source link

Tracing: support jaeger-agent tracer #15429

Open cocotyty opened 3 years ago

cocotyty commented 3 years ago

Title: One line description When we used envoy and jaeger together, we found that envoy does not support sending data directly to jaeger-agent. Description:

Describe the the desired behavior, what scenario it enables and how it would be used.

[optional Relevant Links:]

Any extra documentation required to understand the issue. https://github.com/jaegertracing/jaeger-client-cpp https://www.jaegertracing.io/docs/1.22/architecture/

suniltheta commented 2 years ago

Could this issue be same as https://github.com/envoyproxy/envoy/issues/16401 which is closed due to staleness. May be we should revisit this problem.

I also notice that if we are using latest image from https://hub.docker.com/r/jaegertracing/all-in-one then the zipkin traces sent to this jaeger collector doesn't show up on jaeger UI.

The last working version seem to be jaegertracing/all-in-one:1.21

Checking if https://github.com/jaegertracing/jaeger-operator/issues/1441 is the root cause of the problem.

cc: @darox

suniltheta commented 2 years ago

So setting COLLECTOR_ZIPKIN_HOST_PORT instead of COLLECTOR_ZIPKIN_HTTP_PORT fixed the issue for me. A deprecated variable COLLECTOR_ZIPKIN_HTTP_PORT was removed from v1.22 ref: https://github.com/jaegertracing/jaeger/releases/tag/v1.22.0

suniltheta commented 2 years ago

Hi @cocotyty is this still an issue?