Graphite vs StatsD vs Statsite

Overview

StatsD

Stacks373

Followers293

Votes31

Graphite

Stacks383

Followers419

Votes42

GitHub Stars6.0K

Forks1.3K

Statsite

Stacks4

Followers25

Votes0

Graphite vs StatsD vs Statsite: What are the differences?

Data Storage Mechanism: Graphite stores data in a Whisper database, which is a fixed-size database optimized for insertion speed. StatsD aggregates data on the fly and sends it to a monitoring system, while Statsite uses in-memory storage for metrics before sending it to a backend system.
Aggregation Methods: Graphite focuses on data storage and graphing, while StatsD and Statsite focus on real-time aggregation and transmission of metrics. StatsD offers a range of aggregation methods, such as counting, gauges, timing, and sets, while Statsite provides a more simplified set of aggregation methods.
Programming Language: Graphite is primarily written in Python and relies on web technologies like Django for its frontend, while StatsD is written in Node.js. Statsite is developed in C for high performance and low resource consumption, making it suitable for environments with limited resources.
Data Sampling: StatsD allows for data sampling by specifying a sample rate, which can help reduce the volume of data transmitted to the monitoring system. Graphite does not natively support data sampling, while Statsite has limited support for data sampling based on configuration settings.
Data Transmission Protocol: StatsD uses UDP for sending metrics, which is a connectionless protocol suitable for low-latency, high-throughput data transmission. Graphite supports different protocols like plaintext and pickle for data submission, while Statsite uses TCP for transmitting metrics to backend systems.
Extensibility and Plugins: StatsD has a rich ecosystem of plugins and integrations, making it easy to extend its functionality with third-party tools. Graphite and Statsite have limited plugin support compared to StatsD, which can limit their flexibility in integrating with other systems.

In Summary, Graphite focuses on data storage and visualization, StatsD specializes in real-time aggregation and transmission of metrics, while Statsite excels in high-performance metric processing with low resource usage.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on StatsD, Graphite, Statsite

Susmita

Senior SRE at African Bank

Jul 28, 2020

Needs adviceon

Grafana

Looking for a tool which can be used for mainly dashboard purposes, but here are the main requirements:

Must be able to get custom data from AS400,
Able to display automation test results,
System monitoring / Nginx API,
Able to get data from 3rd parties DB.

Grafana is almost solving all the problems, except AS400 and no database to get automation test results.

869k views869k

Comments

Detailed Comparison

StatsD	Graphite	Statsite
It is 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).	Graphite does two things: 1) Store numeric time-series data and 2) Render graphs of this data on demand	Statsite is a metrics aggregation server. Statsite is based heavily on Etsy's StatsD https://github.com/etsy/statsd, and is wire compatible.
Network daemon; Runs on the Node.js platform; Sends aggregates to one or more pluggable backend services	carbon - a Twisted daemon that listens for time-series data;whisper - a simple database library for storing time-series data (similar in design to RRD);graphite webapp - A Django webapp that renders graphs on-demand using Cairo	Multiple metric types;Efficient summary metrics for timer data;Dynamic set implementation;Binary protocol
Statistics
GitHub Stars -	GitHub Stars 6.0K	GitHub Stars -
GitHub Forks -	GitHub Forks 1.3K	GitHub Forks -
Stacks 373	Stacks 383	Stacks 4
Followers 293	Followers 419	Followers 25
Votes 31	Votes 42	Votes 0
Pros & Cons
Pros 9 Open source 7 Single responsibility 5 Efficient wire format 3 Handles aggregation 3 Loads of integrations Cons 1 No authentication; cannot be used over Internet	Pros 16 Render any graph 9 Great functions to apply on timeseries 8 Well supported integrations 6 Includes event tracking 3 Rolling aggregation makes storage managable	No community feedback yet
Integrations
Node.js Docker	Sensu Nagios Logstash Windows Server Netdata Riemann Diamond Telegraf collectd Ganglia	No integrations available

What are some alternatives to StatsD, Graphite, Statsite?

Grafana

Grafana is a general purpose dashboard and graph composer. It's focused on providing rich ways to visualize time series metrics, mainly though graphs but supports other ways to visualize data through a pluggable panel architecture. It currently has rich support for for Graphite, InfluxDB and OpenTSDB. But supports other data sources via plugins.

Kibana

Kibana is an open source (Apache Licensed), browser based analytics and search dashboard for Elasticsearch. Kibana is a snap to setup and start using. Kibana strives to be easy to get started with, while also being flexible and powerful, just like Elasticsearch.

Prometheus

Prometheus is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true.

Nagios

Nagios is a host/service/network monitoring program written in C and released under the GNU General Public License.

Netdata

Netdata collects metrics per second & presents them in low-latency dashboards. It's designed to run on all of your physical & virtual servers, cloud deployments, Kubernetes clusters & edge/IoT devices, to monitor systems, containers & apps

Zabbix

Zabbix is a mature and effortless enterprise-class open source monitoring solution for network monitoring and application monitoring of millions of metrics.

Sensu

Sensu is the future-proof solution for multi-cloud monitoring at scale. The Sensu monitoring event pipeline empowers businesses to automate their monitoring workflows and gain deep visibility into their multi-cloud environments.

Lumigo

Lumigo is an observability platform built for developers, unifying distributed tracing with payload data, log management, and real-time metrics to help you deeply understand and troubleshoot your systems.

Jaeger

Jaeger, a Distributed Tracing System

Telegraf

It is an agent for collecting, processing, aggregating, and writing metrics. Design goals are to have a minimal memory footprint with a plugin system so that developers in the community can easily add support for collecting metrics.

Related Comparisons

Graphite vs StatsD vs Statsite: What are the differences?

Data Storage Mechanism: Graphite stores data in a Whisper database, which is a fixed-size database optimized for insertion speed. StatsD aggregates data on the fly and sends it to a monitoring system, while Statsite uses in-memory storage for metrics before sending it to a backend system.
Aggregation Methods: Graphite focuses on data storage and graphing, while StatsD and Statsite focus on real-time aggregation and transmission of metrics. StatsD offers a range of aggregation methods, such as counting, gauges, timing, and sets, while Statsite provides a more simplified set of aggregation methods.
Programming Language: Graphite is primarily written in Python and relies on web technologies like Django for its frontend, while StatsD is written in Node.js. Statsite is developed in C for high performance and low resource consumption, making it suitable for environments with limited resources.
Data Sampling: StatsD allows for data sampling by specifying a sample rate, which can help reduce the volume of data transmitted to the monitoring system. Graphite does not natively support data sampling, while Statsite has limited support for data sampling based on configuration settings.
Data Transmission Protocol: StatsD uses UDP for sending metrics, which is a connectionless protocol suitable for low-latency, high-throughput data transmission. Graphite supports different protocols like plaintext and pickle for data submission, while Statsite uses TCP for transmitting metrics to backend systems.
Extensibility and Plugins: StatsD has a rich ecosystem of plugins and integrations, making it easy to extend its functionality with third-party tools. Graphite and Statsite have limited plugin support compared to StatsD, which can limit their flexibility in integrating with other systems.

Graphite vs StatsD vs Statsite

Overview