Statsd alternatives and similar tools
Based on the "Metric & Metric Collection" category.
Alternatively, view Statsd alternatives based on common mentions on social networks and blogs.
9.9 10.0 Statsd VS GrafanaThe open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
9.1 9.9 Statsd VS TelegrafThe plugin-driven server agent for collecting & reporting metrics.
9.1 9.9 Statsd VS Packetbeat:tropical_fish: Beats - Lightweight shippers for Elasticsearch & Logstash
7.9 0.0 L4 Statsd VS FreeboardA damn-sexy, open source real-time dashboard builder for IOT and other web mashups. A free open-source alternative to Geckoboard.
7.0 7.1 L3 Statsd VS CollectdThe system statistics collection daemon. Please send Pull Requests here!
6.0 4.1 L3 Statsd VS DiamondDiamond is a python daemon that collects system metrics and publishes them to Graphite (and others). It is capable of collecting cpu, memory, network, i/o, load and disk metrics. Additionally, it features an API for implementing custom collectors for gathering metrics from almost any source.
3.5 0.0 L3 Statsd VS PGObserverA battle-tested, flexible & comprehensive monitoring solution for your PostgreSQL databases
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Statsd or a related project?
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).
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)
Each stat will have a value. How it is interpreted depends on modifiers. In general values should be integers.
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](./Dockerfile)
- Install Node.js (All
LTSNode.js versions are supported.)
- Clone the project
- Create a config file from
exampleConfig.jsand 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 127.0.0.1 8125
More Specific Topics
- Metric Types
- Graphite Integration
- Supported Servers
- Supported Backends
- Admin TCP Interface
- Server Interface
- Backend Interface
- Metric Namespacing
- StatsD Cluster Proxy
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