Graphite-Cyanite

A plugin for using graphite with the cassandra-based Cyanite storage backend.

Requires Graphite-API (preferred) or Graphite-web 0.10.X.

Graphite-API is available on PyPI. Read the documentation for more information.

Graphite-web 0.10.X is currently unreleased. You'll need to install from source.

Installation

pip install cyanite

Using with graphite-api

In your graphite-api config file:

cyanite:
  urls:
    - http://cyanite-host:port
finders:
  - cyanite.CyaniteFinder

Using with graphite-web

In your graphite's local_settings.py:

STORAGE_FINDERS = (
    'cyanite.CyaniteFinder',
)

CYANITE_URLS = (
    'http://host:port',
)

Where host:port is the location of the Cyanite HTTP API. If you run Cyanite on multiple hosts, specify all of them to load-balance traffic:

# Graphite-API
cyanite:
  urls:
    - http://host1:port
    - http://host2:port

# Graphite-web
CYANITE_URLS = (
    'http://host1:port',
    'http://host2:port',
)

See pyr/cyanite for running the Cyanite carbon daemon.

Changelog

• 0.4.5 (2015-05-05): Handle path matches that return no data.
• 0.4.4 (2014-10-22): Chunk cyanite requests if they end up being too long for cyanite.
• 0.4.3 (2014-05-15): Fix a KeyError when no data is returned by cyanite for a given path.
• 0.4.2 (2014-04-11): Fix graphite-web compatibility when using settings.CYANITE_URLS.
• 0.4.1 (2014-04-10): Fix for multiple fetches when the results are empty.
• 0.4.0 (2014-04-10): Ability to fetch multiple paths at a time instead of sequentially (requires graphite-api).
• 0.3.0 (2014-04-07): Change configuration syntax to allow multiple-node cyanite setups.
• 0.2.1 (2014-03-07): Prevent breaking graphite rendering when no data is returned from cyanite.
• 0.2.0 (2014-03-06): Graphite-API compatibility.
• 0.1.0 (2013-12-08): initial version.