Add Unix Domain Socket Listener to statsdreceiver

[michaelli321]

Component(s)

receiver/statsd

Is your feature request related to a problem? Please describe.

We're currently migrating workloads to use the OTEL Collector for metric collection. The datadog-agent supports ingesting StatsD metrics via a Unix Domain Socket.

Unix Domain Sockets allow you to establish the connection with a socket file, regardless of the IP of the Datadog Agent container. It also enables the following benefits:

• Bypassing the networking stack brings a significant performance improvement for high traffic.
• While UDP has no error handling, UDS allows the Agent to detect dropped packets and connection errors, while still allowing a non-blocking use.
• DogStatsD can detect the container from which metrics originated and tag those metrics accordingly.

Are there plans to also support UDS through the statsdreceiver?

Describe the solution you'd like

Adding a UDS listener to the statsdreceiver

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/statsd: @jmacd @dmitryax

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[michaelli321]

Actually, I see this was already kept in mind when writing the statsdreceiver: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/statsdreceiver/receiver.go#L79

[dmitryax]

Hi, @michaelli321, thanks for reporting. I don't think anyone is planning to work on this in the near future. Feel free to contribute if you have a chance.

[g41797]

Hi
As far as i understand you are talking about server side improvement
What about client?
Now I am in the middle of gavv/httpexpect#246
If this issue isn't urgent I'd like to participate

[g41797]

/label needs-discussion

[g41797]

Thanks

CONTRIBUTING.md: "needs discussion" vs "discussion need"

Run ./.github/workflows/scripts/add-labels.sh
failed to update #21385: 'needs discussion' not found
failed to update 1 issue
Error: Process completed with exit code 1.

[kilokang]

Hi!

I hope that I can have a PR to add this feature in a few days addressing this :)