trace with zipkin

[fanjianfeng2014]

when I enable zipkin plugin, the service name always is default ，not the specific upstream service name.

the other question :
We also use zipkin in dapr, the headers filled by the W3C standard,but it diffierent to APISIX，how to compatibale?
https://www.w3.org/TR/trace-context/

[dmsolr]

first, the service name is irrelated to the upstream service name, so I cannot get your means.
then, do the headers mean the zipkin b3-propagation headers?
If so, I think they are compatible. Because the APISIX fully follows the Zipkin B3 specification

[fanjianfeng2014]

first, the service name is irrelated to the upstream service name, so I cannot get your means.
Is the zipkin report "request -proxy - rewrite" 3 sequential ? not like gateway - serviceA - serviceB ,only in APISIX self?

[dmsolr]

That looks like you don't enable Zipkin on your upstream service. This picture shows the APISIX enabled Zipkin only.
For example, we deployed like Client -> APISIX -> Server, can see following: