You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we are unable to configure the Unix Domain Socket (UDS) to send tracing spans to Datadog. This limitation arises from the DataDogAddress function which only accepts values in the host:port format. Moreover, the Istiod-generated configuration below does not support UDS:
Datadog supports UDS for receiving trace spans. Therefore, we would like to support that send trace spans via UDS to optimize the performance of traceable Istio-proxy.
Describe alternatives you've considered
Affected product area (please put an X in all that apply)
[ ] Ambient
[ ] Docs
[ ] Dual Stack
[ ] Installation
[ ] Networking
[ x ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ x ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context
The text was updated successfully, but these errors were encountered:
mugioka
changed the title
Support for communication via UNIX Domain Socket(UDS) when sending trace spans from istio-proxy to Datadog Agent.
Support for connection via UNIX Domain Socket(UDS) when sending trace spans from istio-proxy to Datadog Agent.
May 2, 2024
Envoy internally uses Datadog integration for C++. Therefore, in order to send tracing spans to the Datadog agent via UDS (Unix Domain Socket), modifications are required to both Envoy and the Datadog C++ tracing library.
Describe the feature request
Currently, we are unable to configure the Unix Domain Socket (UDS) to send tracing spans to Datadog. This limitation arises from the DataDogAddress function which only accepts values in the
host:port
format. Moreover, the Istiod-generated configuration below does not support UDS:From my understanding of the Envoy configuration, config.core.v3.SocketAddress does not support UDS. Therefore, we need to use config.core.v3.Pipe to send the tracing span via UDS.
Datadog supports UDS for receiving trace spans. Therefore, we would like to support that send trace spans via UDS to optimize the performance of traceable Istio-proxy.
Describe alternatives you've considered
Affected product area (please put an X in all that apply)
[ ] Ambient
[ ] Docs
[ ] Dual Stack
[ ] Installation
[ ] Networking
[ x ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ x ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context
The text was updated successfully, but these errors were encountered: