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
We're currently seeing cases where after a week or so where metrics from some of our processes stop reaching Datadog. Restarting the processes will fix the issue, we see metrics land in Datadog immediately following a restart.
We've instrumented the client with an error callback, which is not getting triggered, we don't see any log entries for it. Has anyone else run into something like this or is unique to our experience?
Well that is pretty odd- I haven't heard of this one before. Do you have DD_AGENT_HOST set by any chance, and could that host IP change (and not be picked up because of cacheDns?). Not thinking of anything else from what you show here.
@deweyjose Dealing w/ something slightly similar -- if your maxBufferSize too big? Datadog agent's default buffer is 8KB, and what you have is 10_000 * 2B = 20KB
Hi,
We're currently seeing cases where after a week or so where metrics from some of our processes stop reaching Datadog. Restarting the processes will fix the issue, we see metrics land in Datadog immediately following a restart.
We've instrumented the client with an error callback, which is not getting triggered, we don't see any log entries for it. Has anyone else run into something like this or is unique to our experience?
This is how we're configuring the StatsD client.
We are on version 8.3.0.
NodeJS version 8.9.4.
The text was updated successfully, but these errors were encountered: