graphite-dev team mailing list archive

[Michael Leinartas <question192662@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

Michael Leinartas proposed the following answer:
Generally something is used in front of Graphite to do the aggregation -
statsd (https://github.com/etsy/statsd) or one of its clones is most
popular. I think you'd want to be storing only the aggregate counters
rather than per-user. Graphite is well suited for data which is recorded
over time (e.g. count of users using xmpp) but not so well suited for
very sparse data like I think you'd have reported directly by the plugin
(today this user is using xmpp (binary value)). Using statsd, you'd have
each plugin instance send out "increment users.services.xmpp.count by 1"
at some interval - say, once per day (per client). If you then
summarized the data over a day, you'd have a count of how many users had
an active xmpp account for that day.

If you're looking more for absolute counts, you'd need to deal with it
somewhat differently so as not to double count clients. I think Graphite
might be less suited for this case, though it certainly can be done.

As far as charting, at the moment Graphite is very focused on line
graphs. There is basic support for Pie graphs and there's an out of date
branch out there in lauchpad that adds some basic bar graph support, but
line graphs are where all the features lie. Note that Graphite can also
export raw data in json and csv form for use elsewhere.

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