Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to check if connectivity to Datadog is good #184

Open
tjpeel opened this issue Oct 6, 2022 · 2 comments
Open

How to check if connectivity to Datadog is good #184

tjpeel opened this issue Oct 6, 2022 · 2 comments

Comments

@tjpeel
Copy link

tjpeel commented Oct 6, 2022

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.

@tjpeel 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
@tjpeel
Copy link
Author

tjpeel commented Oct 6, 2022

Perhaps something using ITelemetryCounters and Environment.TickCount64 would suffice in warning if nothing has been sent.

@ogaca-dd
Copy link
Contributor

Hello @tjpeel,

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants