Jaeger and Istio Sidecar Compatibility #1373
Replies: 2 comments 3 replies
-
Hi @AnthonyGurg Currently if you want to have spans reported for the inbound/outbound requests (from the Istio/envoy proxy), and also spans from within the application being traced using Jaeger, then it would be necessary to have both the Istio sidecar and a Jaeger tracer/client reporting spans - either to a sidecar Jaeger agent or directly to the collector. Hopefully in the future, when Istio move to a more OpenTelemetry based approach, it would be possible to have the OpenTelemetry Collector as an agent bundled within the Istio sidecar, and as well as the proxy reporting its own spans, the app would also be able to report its observability data (metrics, logs and traces) to that same sidecar. This would definitely simplify configuration. |
Beta Was this translation helpful? Give feedback.
-
As a sanity check: are you able to get the BookInfo demo working fine? P.S.: if you have an OpenShift subscription (looks like you do), you might want to open a support case instead. We don't have an SLA for support here in the community forum. |
Beta Was this translation helpful? Give feedback.
-
Hi there, I had a question about the sidecar compatibilities.
I'm currently using the Red Hat OSSM 2.0 and OCP 4.6 and I'm normally able to view my traces using the Jaeger operator and the "sidecar.jaegertracing.io/inject: jaeger" annotation. However I'm now wanting to use Kiali as well but when I use the Istio sidecar "sidecar.istio.io/inject: "true"" along with the Jaeger sidecar, I'm no longer able to access my routes for my application.
When I omit the Jaeger sidecar and only use the Istio sidecar, Jaeger does display traces but only the Proxy spans. Am I able to retrieve the traces I'd normally but with only the Istio sidecar, or is there any extra configuration required to be able to use both sidecars?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions