A client for DogStatsD, an extension of the StatsD metric server for Datadog. Full API documentation is available in DogStatsD-ruby rubydoc.

Build Status

See for changes. To suggest a feature, report a bug, or general discussion, open an issue.


First install the library:

gem install dogstatsd-ruby


To instantiate a DogStatsd client:

# Import the library
require 'datadog/statsd'

# Create a DogStatsD client instance.
statsd ='localhost', 8125)
# release resources used by the client instance

Or if you want to connect over Unix Domain Socket:

# Connection over Unix Domain Socket
statsd = '/path/to/socket/file')
# release resources used by the client instance

Find a list of all the available options for your DogStatsD Client in the DogStatsD-ruby rubydoc or in the Datadog public DogStatsD documentation.

Migrating from v4.x to v5.x

If you are already using DogStatsD-ruby v4.x and you want to migrate to a version v5.x, the major change concerning you is the new threading model (please see section Threading model):

In practice, it means two things:

  1. Now that the client is buffering metrics before sending them, you have to manually call the method Datadog::Statsd#flush if you want to force the sending of metrics. Note that the companion thread will automatically flush the buffered metrics if the buffer gets full or when you are closing the instance.

  2. You have to make sure you are either:

  • using singletons instances of the DogStatsD client and not allocating one each time you need one, letting the buffering mechanism flush metrics, or,
  • properly closing your DogStatsD client instance when it is not needed anymore using the method Datadog::Statsd#close to release the resources used by the instance and to close the socket

v5.x Common Pitfalls

Version v5.x of dogstatsd-ruby is using a companion thread for preemptive flushing, it brings better performances for application having a high-throughput of statsd metrics, but it comes with new pitfalls:

* Applications forking after having created the dogstatsd instance: forking a process can't duplicate the existing threads, meaning that one of the processes won't have a companion thread to flush the metrics and will lead to missing metrics.
* Applications creating a lot of different instances of the client without closing them: it is important to close the instance to free the thread and the socket it is using or it will lead to thread leaks.

If you are using Sidekiq, please make sure to close the client instances that are instantiated. See this example on using DogStatsD-ruby v5.x with Sidekiq.

If you are using Puma or Unicorn, please make sure to create the instance of DogStatsD in the workers, not in the main process before it forks to create its workers. See this comment for more details.

Applications that are in these situations and can't apply these recommendations should pin dogstatsd-ruby v4.x using gem 'dogstatsd-ruby', '~> 4.0'. Note that v4.x will continue to be maintained until a future v5.x version can more easily fit these use cases.

Origin detection over UDP

Origin detection is a method to detect which pod DogStatsD packets are coming from in order to add the pod's tags to the tag list.

To enable origin detection over UDP, add the following lines to your application manifest

  - name: DD_ENTITY_ID
        fieldPath: metadata.uid

The DogStatsD client attaches an internal tag, entity_id. The value of this tag is the content of the DD_ENTITY_ID environment variable, which is the pod’s UID.


In order to use DogStatsD metrics, events, and Service Checks the Agent must be running and available.


After the client is created, you can start sending custom metrics to Datadog. See the dedicated Metric Submission: DogStatsD documentation to see how to submit all supported metric types to Datadog with working code examples:

Some options are suppported when submitting metrics, like applying a Sample Rate to your metrics or tagging your metrics with your custom tags. Find all the available functions to report metrics in the DogStatsD-ruby rubydoc.


After the client is created, you can start sending events to your Datadog Event Stream. See the dedicated Event Submission: DogStatsD documentation to see how to submit an event to Datadog your Event Stream.

Service Checks

After the client is created, you can start sending Service Checks to Datadog. See the dedicated Service Check Submission: DogStatsD documentation to see how to submit a Service Check to Datadog.

Maximum packets size in high-throughput scenarios

In order to have the most efficient use of this library in high-throughput scenarios, default values for the maximum packets size have already been set for both UDS (8192 bytes) and UDP (1432 bytes) in order to have the best usage of the underlying network. However, if you perfectly know your network and you know that a different value for the maximum packets size should be used, you can set it with the parameter buffer_max_payload_size. Example:

# Create a DogStatsD client instance.
statsd ='localhost', 8125, buffer_max_payload_size: 4096)

Threading model

On versions greater than 5.0, we changed the threading model of the library so that one instance of Datadog::Statsd could be shared between threads and so that the writes in the socket are non blocking.

When you instantiate a Datadog::Statsd, a companion thread is spawned. This thread will be called the Sender thread, as it is modeled by the Sender class.

This thread is stopped when you close the statsd client (Datadog::Statsd#close). It also means that allocating a lot of statsd clients without closing them properly when not used anymore could lead to a thread leak (even though they will be sleeping, blocked on IO). The communication between the current thread is managed through a standard Ruby Queue.

The sender thread has the following logic (Code present in the method Datadog::Statsd::Sender#send_loop):

while the sender message queue is not closed do
  read message from sender message queue

  if message is a Control message to flush
    flush buffer in connection
  else if message is a Control message to synchronize
    synchronize with calling thread
    add message to the buffer
end while

Most of the time, the sender thread is blocked and sleeping when doing a blocking read from the sender message queue.

We can see that there is 3 different kind of messages:

  • a control message to flush the buffer in the connection
  • a control message to synchronize any thread with the sender thread
  • a message to append to the buffer

There is also an implicit message which is closing the queue as it will stop blocking read from the message queue (if happening) and thus, stop the sender thread.

Usual workflow

You push metrics to the statsd client which writes them quickly to the sender message queue. The sender thread receives those message, buffers them and flushes them to the connection when the buffer limit is reached.


When calling a flush, a specific control message (the :flush symbol) is sent to the sender thread. When finding it, it flushes its internal buffer into the connection.


It is possible to ensure a message has been consumed by the sender thread and written to the buffer by simply calling a rendez-vous right after. This is done when you are doing a synchronized flush (calling Datadog::Statsd#flush with the sync: true option).

This means the current thread is going to sleep and wait for a Queue which is given to the sender thread. When the sender thread reads this queue from its own message queue, it puts a placeholder message in it so that it wakes up the calling thread.

This is useful when closing the application or when checking unit tests.


dogstatsd-ruby is forked from Rein Henrichs original Statsd client.

Copyright (c) 2011 Rein Henrichs. See LICENSE.txt for further details.