er is not in the mesh will be
missing peer attributes like workload name, namespace and labels.
However, if both peers have proxies injected all the labels mentioned
<a href=/v1.17/docs/reference/config/metrics/>here</a> are available in the generated metrics.
When the server workload is out of the mesh, server workload metadata is still
distributed to client sidecar, causing client side metrics to have server workload
metadata labels filled.</p></li><li><p><strong>TCP metadata exchange requires mTLS</stron