Is there anyway to identify the time spent in the sidecar and the time spent in the application separately for a given request? In the Jaeger dashboard, I do see time spent in the istio gateway and then it shows I believe the time spent “in the pod”. However, can the trace be enhanced to break down the latencies by sidecar/proxy and the application?
Interesting question. I’m curious if others have a solution. This sounds like a good feature for Meshery to incorporate.