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
Is there a way to check connectivity to Datadog is good based on the configuration settings?
Having something like this would be useful to include in things like health checks so I can determine if things like custom metrics are being sent. Beyond the Configure call, if say the DD port is wrong, I do not know if connectivity is broken.
I see PR #183 has been added recently. This goes some of the way to being able to identify problems.
However, does anything exist today other than manually wiring up a UDP connection and testing out of band of the client? Not withstanding UDP being connectionless.
The text was updated successfully, but these errors were encountered:
tjpeel
changed the title
How to check is connectivity to Datadog is good
How to check if connectivity to Datadog is good
Oct 6, 2022
In case of a network issue, when using UDP, Socket.SendTo doesn't throw an exception and the number of bytes sent to the socket is the same as the number of bytes to send (At least based on my tests).
I suggest using unix domain socket if it is possible for you. When a packet cannot be sent, the telemetry datadog.dogstatsd.client.packets_dropped is incremented.
Is there a way to check connectivity to Datadog is good based on the configuration settings?
Having something like this would be useful to include in things like health checks so I can determine if things like custom metrics are being sent. Beyond the
Configure
call, if say the DD port is wrong, I do not know if connectivity is broken.I see PR #183 has been added recently. This goes some of the way to being able to identify problems.
However, does anything exist today other than manually wiring up a UDP connection and testing out of band of the client? Not withstanding UDP being connectionless.
The text was updated successfully, but these errors were encountered: