node-statsd
node-statsd copied to clipboard
node.js client for Etsy'd StatsD server
Added `batch` option, if true, the messages are batched either by 20 messages or by 1 second. Message of different kinds could be mixed in the batch. Callbacks for individual...
This is a reworking of https://github.com/joybro/node-dogstatsd/pull/11 to fit into node-statsd and fix up a few things in the event support. With this addition, the only thing missing for DogStatsD is...
So some versions of node have this bug: https://github.com/joyent/node/issues/9261 It is triggered when a clustered node process uses client datagram sockets. There's a workaround to bind your client sockets with...
1. change options to an object. 2. add handleError (we had issue on production) the issue was that one of our statsd server url was change and the whole app...
When creating nodejs' `dgram.Socket` it is bound to all hosts by default. Is this intentional? For public servers it might be a good idea to only bind to specific interfaces...
``` shell > var StatsD = require('node-statsd').StatsD; undefined > var client = new StatsD(); undefined > client.increment('foo', 1, function() { console.log('fin'); }) undefined > client.increment('foo', 1, 1, function() { console.log('fin');...
When not passing a callback to the sending functions (any), DNS errors would result in an exception being thrown like this: ``` events.js:66 throw arguments[1]; // Unhandled 'error' event ^...