|Number of watchers on Github||5|
|Number of open issues||0|
|Open pull requests||0+|
|Closed pull requests||0+|
|Last commit||almost 6 years ago|
|Repo Created||almost 6 years ago|
|Repo Last Updated||almost 2 years ago|
|Organization / Author|
|Do you use graphite-web? Leave a review!|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Trendy new open source projects in your inbox! View examples
Graphite consists of two major components:
Client applications connect to the running carbon-cache.py daemon on port 2003 and send it lines of text of the following format:
my.metric.name value unix_timestamp
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.
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
Specify the user account in
This user must also have write privileges to
First you obviously need to decide what data it is you want to graph with
graphite. The script
examples/example-client.py 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 (http://graphite.wikidot.com).