Question about destination_service and destination_service_name metric labels

[delavet]

Please provide an in-depth description of the question you have: I have found out a strange behavior about the metric labels exported by Kmesh. I'm testing in dual-engine mode. If you explore the tcp traffics and compare the destination_service and destination_service_name labels, you'll see that these two labels are exactly the same: they are Service FQDN.

What do you think about this question?: Istio has explained these two metrics in the documentation about Istio Standard Metrics(https://istio.io/latest/docs/reference/config/metrics/).

Destination Service: This identifies destination service host responsible for an incoming request. Ex: details.default.svc.cluster.local.

Destination Service Name: This identifies the destination service name. Ex: details.

As for Kmesh, I'm not sure if this is a bug, or this is designed by purpose. Therefore I just submit a question here.

A known effection of this issue is that Kiali may draw Service nodes on its traffic graph depends on the destination_service_name label.

Environment:

• Kmesh version: latest
• Others:

[Kuromesi]

/assign