graphite-dev team mailing list archive

[chrismd <question114625@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

chrismd proposed the following answer:
You can do it either way, sending raw counter values or calculating and
sending rates. It usually depends on if you will ever care about the
absolute count value, if not then rates are more convenient because you
can avoid the nonNegativeDerivative() call. But that is the only call
you should need to convert the counter to a rate, is there a reason you
are using a scale() call with a crazy factor?

As for the network side of things, I agree Graphite is not designed like
most network monitoring applications which usually can and do make many
assumptions about the type of data you are viewing. As a result there is
usually a fair bit of boilerplate configuration in graphs for things
like network interface throughput (like applying nonNegativeDerivative),
and this makes browsing metrics in Graphite's browser UI not very fun to
do. The UI can definitely be improved, but either way I think the best
way to use graphite is as a backend for a custom UI. Many users make
their own dashboard pages that embed graphite graphs. Doing this with a
scripting language can reduce the repetitive configuration woes and
obviously gives you a lot more control.

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