Skip to content
Branch: master
Find file Copy path
Find file Copy path
17 contributors

Users who have contributed to this file

@LewisMcMahon @draco2003 @mrtazz @yahonggu @OleMchls @hit9 @sysadminmike @markkimsal @themasch @camitz @mark-ezhkov @katzj @chmac @BlueHatbRit @DazWilkin @aurrelhebert @apankrat
63 lines (54 sloc) 3.57 KB

Supported Backends

StatsD supports pluggable backend modules that can publish statistics from the local StatsD daemon to a backend service or data store. Backend services can retain statistics in a time series data store, visualize statistics in graphs or tables, or generate alerts based on defined thresholds. A backend can also correlate statistics sent from StatsD daemons running across multiple hosts in an infrastructure.

StatsD includes the following built-in backends:

  • Graphite (graphite): An open-source time-series data store that provides visualization through a web-browser.
  • Console (console): Outputs the received metrics to stdout (see what's going on during development).
  • Repeater (repeater): Utilizes the packet emit API to forward raw packets retrieved by StatsD to multiple backend StatsD instances.

By default, the graphite backend will be loaded automatically. Multiple backends can be run at once. To select which backends are loaded, set the backends configuration variable to the list of backend modules to load.

Backends are just npm modules which implement the interface described in section Backend Interface. In order to be able to load the backend, add the module name into the backends variable in your config. As the name is also used in the require directive, you can load one of the provided backends by giving the relative path (e.g. ./backends/graphite).

A robust set of are also available as plugins to allow easy reporting into databases, queues and third-party services.

Available Third-party backends

You can’t perform that action at this time.