Tools That Work With Graphite

Collection

Brubeck_ A statsd-compatible stats aggregator written in C.

Bucky_ A small service implemented in Python for collecting and translating metrics for Graphite. It can currently collect metric data from CollectD daemons and from StatsD clients.

Carbonator Windows Service <https://github.com/CryptonZylog/carbonator>_ Simple lightweight Windows Service that collects Performance Counter metrics and sends them over to the Graphite server. Configured via .NET xml application configuration.

collectd_ A daemon which collects system performance statistics periodically and provides mechanisms to store the values in a variety of ways, including RRD. To send collectd metrics into carbon/graphite, use collectd's write-graphite_ plugin (available as of 5.1). Other options include:

Jordan Sissel's node collectd-to-graphite_ proxy
Joe Miller's perl collectd-graphite_ plugin
Gregory Szorc's python collectd-carbon_ plugin
Paul J. Davis's Bucky_ service

Graphite can also read directly from collectd_'s RRD files. RRD files can simply be added to STORAGE_DIR/rrd (as long as directory names and files do not contain any . characters). For example, collectd's host.name/load/load.rrd can be symlinked to rrd/collectd/host_name/load/load.rrd to graph collectd.host_name.load.load.{short,mid,long}term.

Collectl_ A collection tool for system metrics that can be run both interactively and as a daemon and has support for collecting from a broad set of subsystems. Collectl includes a Graphite interface which allows data to easily be fed to Graphite for storage.

Diamond_ a Python daemon that collects system metrics and publishes them to Graphite. 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.

Ganglia_ A scalable distributed monitoring system for high-performance computing systems such as clusters and Grids. It collects system performance metrics and stores them in RRD, but now there is an add-on <https://github.com/ganglia/ganglia_contrib/tree/master/graphite_integration/>_ that allows Ganglia to send metrics directly to Graphite. Further integration work is underway.

graphite-pollers <https://github.com/phreakocious/graphite-pollers>_ A collection of scripts that shovel data into Graphite including a multi-threaded SNMP poller for network interface IF-MIB statistics and another which pulls linux network stack data from files in /proc/net. Add to cron and go.

Graphite PowerShell Functions <https://github.com/MattHodge/Graphite-PowerShell-Functions>_ A group of functions that can be used to collect Windows Performance Counters and send them over to the Graphite server. The main function can be run as a Windows service, and everything is configurable via an XML file.

HoardD_ A Node.js app written in CoffeeScript to send data from servers to Graphite, much like collectd does, but aimed at being easier to expand and with less footprint. It comes by default with basic collectors plus Redis and MySQL metrics, and can be expanded with JavaScript or CoffeeScript.

Host sFlow_ An open source implementation of the sFlow protocol (https://sflow.org), exporting a standard set of host cpu, memory, disk and network I/O metrics. The sflow2graphite utility converts sFlow to Graphite's plaintext protocol, allowing Graphite to receive sFlow metrics.

jmx2graphite_ The easiest way to poll JMX metrics and write them to Graphite. This tool runs as a Docker container, polling your JMX every X seconds and writing the metrics to Graphite. Requires a minimum of configuration to get started.

jmxtrans_ A powerful tool that performs JMX queries to collect metrics from Java applications. It is requires very little configuration and is capable of sending metric data to several backend applications, including Graphite.

Logster_ A utility for reading log files and generating metrics in Graphite or Ganglia. It is ideal for visualizing trends of events that are occurring in your application/system/error logs. For example, you might use logster to graph the number of occurrences of HTTP response code that appears in your web server logs.

metrics-sampler_ A java program which regularly queries metrics from a configured set of inputs, selects and renames them using regular expressions and sends them to a configured set of outputs. It supports JMX and JDBC as inputs and Graphite as output out of the box.

netdata_ A fast and efficient monitoring agent that supports graphite backends. It has collection, forwarding, visualization and monitoring features. Netdata collects common system metrics and a variety of other sources through plugins.

Promitor_ Bringing Azure Monitor metrics where you need them, allowing you to push Azure Monitor metrics to a variety of metric sinks such as a StatsD server.

Sensu_ A monitoring framework that can route metrics to Graphite. Servers subscribe to sets of checks, so getting metrics from a new server to Graphite is as simple as installing the Sensu client and subscribing.

snort2graphite_ Snort IDS/IPS can be configured to generate a rich set of metrics about network traffic. Presently there are more than 130 metrics available. Snort2graphite will pick up the most recent data from your snort.stats file and send all the metrics into Graphite.

SqlToGraphite_ An agent for windows written in .net to collect metrics using plugins (WMI, SQL Server, Oracle) by polling an endpoint with a SQL query and pushing the results into graphite. It uses either a local or a centralised configuration over HTTP.

SSC Serv_ A Windows service (agent) which periodically publishes system metrics, for example CPU, memory and disk usage. It can store data in Graphite using a naming schema that's identical to that used by collectd.

telegraf_ Telegraf is an agent written in Go for collecting, processing, aggregating, and writing metrics. It also supports metric output to Graphite.

Forwarding

Backstop_ A simple endpoint for submitting metrics to Graphite. It accepts JSON data via HTTP POST and proxies the data to one or more Carbon/Graphite listeners.

carbon-c-relay_ Enhanced C implementation of Carbon relay, aggregator and rewriter.

carbon-proxy_ Relay metrics to a carbon daemon, using kafka as middleware. Payload windowing, transformation, duplication, or other custom functions.

carbon-relay-ng_ Fast carbon relay+aggregator with admin interfaces for making changes online - production ready.

Evenflow_ A simple service for submitting sFlow datagrams to Graphite. It accepts sFlow datagrams from multiple network devices and proxies the data to a Carbon listener. Currently only Generic Interface Counters are supported. All other message types are discarded.

Grafsy_ Very light caching proxy for graphite metrics with additional features:

Caching metrics in case of outage and sending them later
Validation of metrics
Aggregating of metrics, including SUM and AVG functions
Much more

Graphite-Newrelic_ Get your graphite data into New Relic_ via a New Relic Platform plugin.

Graphite-relay_ A fast Graphite relay written in Scala with the Netty framework.

Graphios_ A small Python daemon to send Nagios performance data (perfdata) to Graphite.

Graphout_ A Node.js application that lets you forward Graphite based queries (using the render API) out to different external services. There are built in modules for Zabbix and CloudWatch. Custom modules are very easy to write.

Grockets_ A node.js application which provides streaming JSON data over HTTP from Graphite.

Gruffalo_ An asynchronous Netty based graphite proxy, for large scale installations. It protects Graphite from the herds of clients by minimizing context switches and interrupts; by batching and aggregating metrics. Gruffalo also allows you to replicate metrics between Graphite installations for DR scenarios, for example.

Ledbetter_ A simple script for gathering Nagios problem statistics and submitting them to Graphite. It focuses on summary (overall, servicegroup and hostgroup) statistics and writes them to the nagios.problems metrics namespace within Graphite.

pipe-to-graphite_ A small shell script that makes it easy to report the output of any other cli program to Graphite.

Polymur_ A fast relay and HTTPS forwarder toolset written in Go.

statsd_ A simple daemon for easy stats aggregation, developed by the folks at Etsy. A list of forks and alternative implementations can be found at https://joemiller.me/2011/09/list-of-statsd-server-implementations/

Statusengine_ A daemon written in PHP to store Nagios and Naemon performance data to Graphite.

Visualization

Charcoal_ A simple Sinatra dashboarding frontend for Graphite or any other system status service which can generate images directly from a URL. Charcoal configuration is driven by a YAML config file.

Descartes_ A Sinatra-based dashboard that allows users to correlate multiple metrics in a single chart, review long-term trends across one or more charts, and to collaborate with other users through a combination of shared dashboards and rich layouts.

Dusk_ A simple dashboard for isolating "hotspots" across a fleet of systems. It incorporates horizon charts using Cubism.js to maximize data visualization in a constrained space.

Firefly_ A web application aimed at powerful, flexible time series graphing for web developers.

Gdash_ A simple Graphite dashboard built using Twitters Bootstrap driven by a small DSL.

Giraffe_ A Graphite real-time dashboard based on Rickshaw_ and requires no server backend. Inspired by Gdash, Tasseo and Graphene_ it mixes features from all three into a slightly different animal.

Grafana_ A general purpose graphite dashboard replacement with feature rich graph editing and dashboard creation interface. It contains a unique Graphite target parser that enables easy metric and function editing. Fast client side rendering (even over large time ranges) using Flot with a multitude of display options (Multiple Y-axis, Bars, Lines, Points, smart Y-axis formats and much more). Click and drag selection rectangle to zoom in on any graph.

Graphene_ A Graphite dashboard toolkit based on D3.js_ and Backbone.js_ which was made to offer a very aesthetic realtime dashboard. Graphene provides a solution capable of displaying thousands upon thousands of datapoints all updated in realtime.

graphite-dashboardcli_ A tool for manage graphite dashboards from command line:

import\Export dashboards from\to Graphite servers
synchronize dashboards between multiple Graphite servers
keep dashboards in YAML format

Graphite-Tattle_ A self-service dashboard frontend for Graphite and Ganglia_.

Graphiti_ A powerful dashboard front end with a focus on ease of access, ease of recovery and ease of tweaking and manipulation.

Graphitoid_ An Android app which allows one to browse and display Graphite graphs on an Android device.

graphitus_ A client side dashboard for graphite built using bootstrap and underscore.js.

Graphsky_ A flexible and easy to configure PHP based dashboard. It uses JSON template files to build graphs and specify which graphs need to be displayed when, similar to Ganglia-web. Just like Ganglia, it uses a hierarchial structure: Environment/Cluster/Host/Metric to be able to display overview graphs and host-specific metrics. It communicates directly to the Graphite API to determine which Environments, Clusters, Hosts and Metrics are currently stored in Graphite.

Graph-Explorer_ A graphite dashboard which uses plugins to add tags and metadata to metrics and a query language with lets you filter through them and compose/manipulate graphs on the fly. Also aims for high interactivity using TimeseriesWidget_ and minimal hassle to set up and get running.

Graph-Index_ An index of graphs for Diamond_.

Hubot_ A Campfire bot written in Node.js and CoffeeScript. The related hubot-scripts_ project includes a Graphite script which supports searching and displaying saved graphs from the Composer directory in your Campfire rooms.

Leonardo_ A Graphite dashboard inspired by Gdash. It's written in Python using the Flask framework. The interface is built with Bootstrap. The graphs and dashboards are configured through the YAML files.

Orion_ A powerful tool to create, view and manage dashboards for your Graphite data. It allows easy implementation of custom authentication to manage access to the dashboard.

Pencil_ A monitoring frontend for graphite. It runs a webserver that dishes out pretty Graphite URLs in interesting and intuitive layouts.

Targets-io_ A dashboard application for organizing, analyzing, benchmarking and reporting of performance test results. All performance test metrics are stored in Graphite and can be benchmarked between test runs, providing automated feedback on the performance of an application.

Tasseo_ A lightweight, easily configurable, real-time dashboard for Graphite metrics.

Terphite_ Terminal tool for displaying Graphite metrics.

Tessera_ A flexible front-end for creating dashboards with a wide variety of data presentations.

TimeseriesWidget_ Adds timeseries graphs to your webpages/dashboards using a simple api, focuses on high interactivity and modern features (realtime zooming, datapoint inspection, annotated events, etc). Supports Graphite, flot, rickshaw and anthracite.

Monitoring

Cabot_ A self-hosted monitoring and alerting server that watches Graphite metrics and can alert on them by phone, SMS, Hipchat or email. It is designed to be deployed to cloud or physical hardware in minutes and configured via web interface.

graphite-beacon_ A simple alerting application for Graphite. It asynchronous and sends notification alerts based on Graphite metrics. It hasn't any dependencies except Tornado package. Very light and really very easy deployed.

graphite-to-zabbix_ A tool to make zabbix alerts based on Graphite data.

Icinga_ Icinga 2 will directly write metrics to the defined Graphite Carbon daemon tcp socket if the graphite feature is enabled. This feature is a more simple integration compared to Icinga 1.x and Graphios.

Moira_ An alerting system based on Graphite data. Moira is a real-time alerting tool, independent from graphite storage, custom expressions and extendable notification channels.

rearview_ A real-time monitoring framework that sits on top of Graphite's time series data. This allows users to create monitors that both visualize and alert on data as it streams from Graphite. The monitors themselves are simple Ruby scripts which run in a sandbox to provide additional security. Monitors are also configured with a crontab compatible time specification used by the scheduler. Alerts can be sent via email, pagerduty, or campfire.

Rocksteady_ A system that ties together Graphite, RabbitMQ, and Esper. Developed by AdMob (who was then bought by Google), this was released by Google as open source (https://opensource.googleblog.com/2010/09/get-ready-to-rocksteady.html).

Seyren_ An alerting dashboard for Graphite.

Shinken_ A system monitoring solution compatible with Nagios which emphasizes scalability, flexibility, and ease of setup. Shinken provides complete integration with Graphite for processing and display of performance data.

Skyline_ An anomaly detection/deflection system that receives all Graphite metrics data in real time via a carbon-relay pickle and analyses each time series to detect anomalies, drops off cliffs, user defined thresholds, handles multiple seasonality, records all anomalies and cross correlates all metrics to anomalies for the purpose of root cause analysis. Skyline can also be trained on what is not anomalous and thereafter it can independently learn what is not anomalous using a time series similarities comparison method. It can alert via smtp, hipchat and pagerduty.

Storage Backend Alternates

If you wish to use a backend to graphite other than Whisper, there are some options available to you.

BigGraphite_ A time-series database written in Python on top of Cassandra. It integrates with Graphite as a plugin.

carbon-clickhouse_ Graphite metrics receiver with ClickHouse_ as storage. You will also need graphite-clickhouse_ as backend for Graphite-web.

cassabon_ Carbon daemon using Cassandra as the backend, implemented in Go. It also acts as an API for Graphite (using the Cyanite_ reader) to retrieve the stats to display.

Ceres_ An alternate storage backend provided by the Graphite Project. It it intended to be a distributable time-series database. It is currently in a pre-release status.

Cyanite_ A highly available, elastic, and low-latency time-series storage written on top of Cassandra

hisser_ Time series database, backend for graphite, fast alternative to carbon + whisper.

graphite-clickhouse_ Graphite-web backend with ClickHouse_ support. Please also see carbon-clickhouse_.

Graphouse_ Graphouse allows you to use ClickHouse_ as a Graphite storage.

go-carbon_ Golang implementation of Graphite/Carbon server with classic architecture: Agent -> Cache -> Persister.

influxgraph_ Graphite InfluxDB_ backend. InfluxDB_ storage finder / plugin for Graphite API.

Kenshin_ A time-series database alternative to Graphite Whisper with 40x improvement in IOPS. It integrates with Graphite as a plugin.

metrictank_ Cassandra-backed, metrics2.0 based, multi-tenant timeseries database for Graphite and friends.

Other

bosun_ Time Series Alerting Framework. Can use Graphite as time series source.

carbonapi_ 3rd party reimplementation of graphite-web in Go, which supports a significant subset of graphite functions. In some testing it has shown to be 5x-10x faster than requesting data from graphite-web.

Bryans-Graphite-Tools_ A collection of miscellaneous scripts for pulling data from various devices, F5, Infoblox, Nutanix, etc.

buckytools_ Go implementation of useful tools for dealing with Graphite's Whisper DBs and Carbon hashing.

carbonate_ Utilities for managing graphite clusters.

go-graphite buckytools_ Fork of buckytools_, with more features.

graphite-dl4j_ Experimental: Train a model for predictions. Machine learning using data from graphite.

graphite-remote-adapter_ Fully featured graphite remote adapter for Prometheus_.

riemann_ A network event stream processing system, in Clojure. Can use Graphite as source of event stream.

Therry_ A simple web service that caches Graphite metrics and exposes an endpoint for dumping or searching against them by substring.