Need help with statsd?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

16.0K Stars 2.0K Forks MIT License 1.0K Commits 85 Opened issues


Daemon for easy but powerful stats aggregation

Services available


Need anything else?

Contributors list

StatsD Build Status Join the chat at Docker Pulls

A network daemon that runs on the Node.js platform and listens for statistics, like counters and timers, sent over UDP or TCP and sends aggregates to one or more pluggable backend services (e.g., Graphite).

Key Concepts

  • buckets

Each stat is in its own "bucket". They are not predefined anywhere. Buckets can be named anything that will translate to Graphite (periods make folders, etc)

  • values

Each stat will have a value. How it is interpreted depends on modifiers. In general values should be integers.

  • flush

After the flush interval timeout (defined by

, default 10 seconds), stats are aggregated and sent to an upstream backend service.

Installation and Configuration


StatsD supports docker in two ways: * The official docker image on docker hub * Building the image from the bundled Dockerfile

Manual installation

  • Install Node.js (All
    Node.js versions
    are supported.)
  • Clone the project
  • Create a config file from
    and put it somewhere
  • Start the Daemon:
    node stats.js /path/to/config


The basic line protocol expects metrics to be sent in the format:


So the simplest way to send in metrics from your command line if you have StatsD running with the default UDP server on localhost would be:

echo "foo:1|c" | nc -u -w0 8125

More Specific Topics


There are additional config variables available for debugging:

  • debug
    - log exceptions and print out more diagnostic info
  • dumpMessages
    - print debug info on incoming messages

For more information, check the



A test framework has been added using node-unit and some custom code to start and manipulate StatsD. Please add tests under test/ for any new features or bug fixes encountered. Testing a live server can be tricky, attempts were made to eliminate race conditions but it may be possible to encounter a stuck state. If doing dev work, a

killall statsd
will kill any stray test servers in the background (don't do this on a production machine!).

Tests can be executed with



StatsD was originally written at Etsy and released with a blog post about how it works and why we created it.


StatsD was inspired (heavily) by the project of the same name at Flickr. Here's a post where Cal Henderson described it in depth: Counting and timing. Cal re-released the code recently: Perl StatsD

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.