[statsd] Fix dedicated-endpoint telemetry shipping when used with UDP

sgnn7 commented 2 years ago

What does this PR do?

Old code had a miswritten function name for telemetry UDP socket creation when separate endpoints were used for the client vs telemetry. This change fixes the issue and adds additional tests around dedicated telemetry socket operations.

Fixes https://github.com/DataDog/datadogpy/issues/689

Description of the Change

Fixes telemetry shipping to dedicated UDP endpoint
Adds logging of unexpected socket errors to stdout
Adds tests around dedicated telemetry socket creation logic

Alternate Designs

N/A

Possible Drawbacks

N/A

Verification Process

See linked issue for reproduction steps

Additional Notes

N/A

Release Notes

N/A

Review checklist (to be filled by reviewers)

[ ] Feature or bug fix MUST have appropriate tests (unit, integration, etc...)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have one changelog/ label attached. If applicable it should have the backward-incompatible label attached.
[ ] PR should not have do-not-merge/ label attached.
[ ] If Applicable, issue must have kind/ and severity/ labels attached at least.

sgnn7 commented 2 years ago

/azp run

azure-pipelines[bot] commented 2 years ago

Azure Pipelines successfully started running 2 pipeline(s).

sgnn7 commented 2 years ago

/azp run

azure-pipelines[bot] commented 2 years ago

Azure Pipelines successfully started running 2 pipeline(s).

sgnn7 commented 2 years ago

/azp run

azure-pipelines[bot] commented 2 years ago

Azure Pipelines successfully started running 2 pipeline(s).

sgnn7 commented 2 years ago

The integration pipeline failures are consistent but unrelated to the change (api, dogshell)

DataDog / datadogpy