Missing span ID 0000000000000000

[vimoj2]

Hello Team,

I am encountering an issue in our GCP environment where a span ID appears as 0000000000000000 in the tracing explorer. It seems anomalous, as I expect all spans to have valid identifiers.

I've attempted two different service mesh installations: the Managed Anthos Service Mesh and a self-managed Istio operator. Unfortunately, the issue persists with both methods. It's worth noting that while application-generated traces appear correctly, there is consistently a missing span ID (0000000000000000) at the top of the hierarchy. I suspect that the ingress Istio gateway deployment might not be transmitting it properly.

Could you advise on how to resolve this issue?

Thank you for your assistance.

 

Istio operator configuration:

apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  meshConfig:
    enableTracing: true
    defaultConfig:
      tracing:
        sampling: 100.0
  profile: default
  components:
    ingressGateways:
      - name: istio-ingressgateway
        enabled: false
      - name: ingress
        enabled: true
        k8s:
          overlays:
            - kind: ServiceAccount
              name: ingress-service-account
              patches:
                - path: metadata.annotations.iam\.gke\.io/gcp-service-account
                  value: SA@PROEJECT_ID.iam.gserviceaccount.com
    cni:
      enabled: true
    pilot:
      enabled: true
      k8s:
        overlays:
          - kind: ServiceAccount
            name: istiod
            patches:
              - path: metadata.annotations.iam\.gke\.io/gcp-service-account
                value: SA@PROEJECT_ID.iam.gserviceaccount.com
  values:
    telemetry:
      enabled: true
      v2:
        stackdriver:
          enabled: true
    pilot:
      traceSampling: 100