service name is always unknown

[yuquan-wang]

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• Question or discussion

---

Question

• What do you want to know?
  I use openTelemetry-collector to export jaeger traces to skywalking-collectors, and i deployed skywalking-kubernetes in my k8s cluster, i can see traces in skywalking UI correctly, except for the service name, here's the screen for the trace:
  
  

note the exported traces can be correctly shown in jaeger UI, so i'm thinking if i missed anything?(I already enable jaeger receiver)
Thanks in advance!

[wu-sheng]

You need to check why Jeager missed the service name

[yuquan-wang]

You need to check why Jeager missed the service name

@wu-sheng thanks for quick reply! if Jaeger missed the service name, then how could it show that in its UI?

My guess is skywalking and Jaeger may be checking different field for "service name"?

[wu-sheng]

Service name used to be an official field. I don't know whether it changes. Jaeger is not our high priority task. Especially, as we have SkyWalking go SDK.