We added tracing to our Spring services running in GKE and it’s working great. But currently the trace list shows a “missing span” message for every single trace.
After looking into it, the missing span is the root-span that is created by the load-balancer. It shows up in the x-cloud-trace-context header coming from the LB and is references in the load-balancer log-message (type.googleapis.com/google.cloud.loadbalancing.type.LoadBalancerLogEntry).
It looks like the load balancer does not however, report the span to Google Cloud Trace. Is there something else i need to do for that?
By the looks of it, the load balancer does not have the necessary context to report the trace spans. One workaround I can suggest is to consider using a different load balancer that supports OpenCensus or OpenTracing. For example, you can use the Istio load balancer, which supports OpenTracing.
To configure Istio to report trace spans:
Install Istio in your GKE cluster.
Enable tracing in Istio by adding the following lines to your istioctl manifest apply command: