It seems envoy has implemented the Kafka protocol filter. Is there any plans to bring the Kafka protocol support to Istio side so that we don’t have to manually implement opentracing to our applications?
Similar to what Istio did for HTTP (where the sidecar containers are the one sending the data to Jaeger/ZipKin), is there any configuration in the meantime or workaround to enable similar behind the scenes tracing on Istio level?
+1 for something that works out of the box.
I’m currently working on seeing traces over Kiali graph but traces path stop with TCP traffic. Perhaps it’s possible to add an EnvoyFilter for that, but if it can come bundled in istio that would be even greater.
I’m interested. Is there any news on this feature?
I’m not aware of anything natively supported. So in the meantime you can instrument the code in producers and consumers, I wrote a little about this here: Trace my mesh (part 3/3). A Distributed Tracing walk-through with… | by Joel Takvorian | Kiali | Medium . Basically it’s just a matter of propagating trace context via kafka headers.