 the Envoy proxies
by adding a specific HTTP header for HTTP protocol or augmenting
ALPN protocol for TCP protocol as described
<a href=/v1.16/docs/tasks/observability/metrics/tcp-metrics/#understanding-tcp-telemetry-collection>here</a>.
This requires Envoy proxies to be injected at both the client & server workloads,
implying that the telemetry reported when one peer is not in the mesh will be
missing peer attributes like workload name, namespace and labels.
However, if both peers have proxies injected all