Missing Linkerd Traces

[jseiser]

1. We have linkerd configured to send traces to Grafana Alloy
2. Our Nginx Ingress is meshed, as is all of our upstream services.
3. We have configured alloy to associated spans to traces using k8s.namespace.name, and k8s.pod.name, we also rename the span attributes coming from linkerd

            `replace_all_patterns(attributes, "key", "linkerd.io/workload-ns", "k8s.namespace.name")`,
            `replace_all_patterns(attributes, "key", "host.name", "k8s.pod.name")`,

4. This matches the default config that linkerd shows in linkerd-jaeger
5. A large majority of our traces will not include linkerd in/out traces, but a small percentage will.

Not really sure how to troubleshoot this, since we know spans arrive, we know they get renamed to match the associations.