Skip to content
git-bzr mirror of graphite trunk
Python JavaScript Other
Find file
Failed to load latest commit information.
bin Fix python2.4 compatibility for
carbon Fix syntax errors in r760
docs Merge in obfuscurity/graphite@3603286
examples fixed Bug #860801
misc fixed some issues from Question #89138
whisper Make two windows in dashboard modal
.bzrignore ignore common cruft
INSTALL updated INSTALL to reference mod_wsgi
LICENSE Add copyright holder to LICENSE making self-inclusive to fix Bug #876991
README more minor deployment fixes Changed to fix Bug #986737.
requirements.txt update bundled pytz
setup.cfg yay i finally have distutils working decently... various cleanups, fixed a regression with, added mor…


Graphite consists of two major components

 1) the frontend Django webapp that runs under mod_python Apache
 2) the backend daemon

Client applications connect to the running daemon on port 2003 and send it
lines of text of the following format:

" value unix_timestamp", for example:

"performance.servers.www01.cpuUsage 42.5 1208815315"

The metric name is like a filesystem path that uses . as a separator instead of /
The value is some scalar integer or floating point value
The unix_timestamp is unix epoch time, as an integer

Each line like this corresponds to one data point for one metric.

Once you've got some clients sending data to carbon-cache, you can view
graphs of that data in the frontend webapp.

 Webapp Installation
Use the instructions in the INSTALL file.

First you must tell carbon-cache what user it should run as.
This must be a user with write privileges to $GRAPHITE_ROOT/storage/whisper/
Specify the user account in $GRAPHITE_ROOT/carbon/conf/carbon.conf

This user must also have write privileges to $GRAPHITE_ROOT/storage/log/carbon-cache/

 Writing a client
First you obviously need to decide what data it is you want to graph with
graphite. The script examples/ demonstrates a simple client
that sends loadavg data for your local machine to carbon on a minutely basis.

The default storage schema stores data in one-minute intervals for 2 hours.
This is probably not what you want so you should create a custom storage schema
according to the docs on the graphite wiki (
Something went wrong with that request. Please try again.