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
My team is currently working on exporting traces over a Unix Domain Socket (UDS). We have a Kubernetes cluster that sets up auto-mount unix sockets to send traces to an agent running on another Kubernetes worker. AFAIK the crate only works over TCP.
What component are you working with?
opentelemetry-datadog
Describe the solution you'd like:
I noticed an example in lib.rs uses a hyperlocal::UnixConnector. However, I don't see an example on how to plug that in to the pipeline. I noticed that some code appends the path with a version field, so not sure if UDS paths are natively supported.
Is it possible to allow this? If so, am I just missing something simple in the example?
Considered Alternatives
I was able to get a rough solution working with socat on my http client's TCP port. Would be great to support UDS out of the box.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Related Problems?
Hello,
My team is currently working on exporting traces over a Unix Domain Socket (UDS). We have a Kubernetes cluster that sets up auto-mount unix sockets to send traces to an agent running on another Kubernetes worker. AFAIK the crate only works over TCP.
What component are you working with?
opentelemetry-datadog
Describe the solution you'd like:
I noticed an example in lib.rs uses a
hyperlocal::UnixConnector
. However, I don't see an example on how to plug that in to the pipeline. I noticed that some code appends the path with a version field, so not sure if UDS paths are natively supported.Is it possible to allow this? If so, am I just missing something simple in the example?
Considered Alternatives
I was able to get a rough solution working with
socat
on my http client's TCP port. Would be great to support UDS out of the box.Additional Context
No response
The text was updated successfully, but these errors were encountered: