Kuma supports only HTTP tracing - what is the root cause?

Hi Guys,

Following this document - https://kuma.io/docs/0.7.2/policies/traffic-trace/#traffic-trace, it seems kuma can only trace traffic for HTTP services. All the TCP services automatically get tagged as “kuma.io/protocol: tcp” ( which is fine ) and traffic for the same does not appear in tracing backend.

Questions:
Is there a specific reason why only HTTP traffic is traceable and not TCP?
Is there a way to enable tracing HTTP traffic even if the port is marked as a TCP port in kuma annotations?

Hey, Kuma maintainer here.

You can find the question here TCP/gRPC Tracing [Question/Feature Request] · Issue #1119 · kumahq/kuma · GitHub
You need to pass additional metadata to every request, it is very difficult to do this with just TCP.

You need to mark a port with HTTP, so Envoy can be configured with HTTP and Tracing can be added.
Here is the doc on how to do it Protocol support in Kuma | Kuma