graphite-dev team mailing list archive

[chrismd <question141393@xxxxxxxxxxxxxxxxxxxxx>]

Question #141393 on Graphite changed:
https://answers.launchpad.net/graphite/+question/141393

    Status: Open => Answered

chrismd proposed the following answer:
RRD support isn't a "major focus" per se, but it is a simple enough to
implement and very convenient for many users so this is definitely
something we should fix. A while back I split Graphite into 3 separate
packages: the webapp, carbon (storage backend), and whisper (db library)
precisely so they could be used independently where it makes sense to do
so. If you've already got a good solution in place that stores your data
in RRD files, then by all means continue using that. You should still be
able to use the Graphite webapp as a frontend to your data (once we fix
this bug of course).

However if you're looking for different characteristics with your
storage system, then carbon/whisper may be a good solution for you.
There is one particular advantage that Graphite offers when used in
conjunction with carbon/whisper that is not possible when Graphite is
used on top of RRD files, and that is that graphs can still display
real-time data even if the system is under high enough load that many
datapoints are being buffered. Also carbon provides a very simple API
for inputting new metrics. But like I said, don't feel like you have to
switch your backend just because you're using Graphite's frontend.

I will make sure this bug is fixed for the next release.

-- 
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.