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?


© 2019 Kong Inc.    Terms  •  Privacy  •  FAQ