Add constructor from existing UDP socket #51
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Sometimes users might want to start a new process in sandboxed environment without network access, for example from systemd PrivateNetwork or any other userspace sandboxing using network namespaces.
In such environment it is not possible to open a new UDP socket to datadog daemon, the only way to get connectivity outside of the sandbox is by using inherited file descriptors. For example from sd_listen_fds
Proposed solution
Client
from a UDP socket. The socket itself could be created from raw file descriptor.