4 ms·

FWIW I've found influxdb considerably easier to install and manage than graphite (graphite doesn't play well with virtualenv, which makes dependency management

by Shish2k 12y ago

FWIW I've found influxdb considerably easier to install and manage than graphite (graphite doesn't play well with virtualenv, which makes dependency management horrible, compared to influxdb's single static binary) Also, I can see logging dictionaries being much more efficient and useful than logging single values -- with graphite if you want to track page hits per section of your site (of which you have 10) per user (100) per browser (5), you end up with 5000 individual metrics, and you need to have thought of them in advance. With influxdb you can log {"section": "front page", "user": "bob", "browser": "firefox", "hits": 1} as a single metric and then use an SQL-like query to filter by section / user / browser (or any combination of those) as and when you want to. TBH the only thing I miss going from graphite to influxdb+grafana is the tree of metrics (grafana has autocomplete once you start typing, but you can't just browse) and a few of the rendering functions (moving average).

pauldix 12y ago
I think the tagging features in the upcoming 0.9.0 release [1] will help with the navigation of metrics. With that we're adding new types of queries to help in discovery. [2] [1] - http://influxdb.com/blog/2014/12/08/clustering_tags_and_enhancements_in_0_9_0.html http://influxdb.com/blog/2014/12/08/clustering_tags_and_enha... [2] - https://github.com/influxdb/influxdb/blob/master/QUERIES.md#list https://github.com/influxdb/influxdb/blob/master/QUERIES.md#...
the_vincedent 12y ago
Totally in the InfluxDB camp too. I've spent the last week working on upgrading our Graphite system. I ultimately killed it and went with InfluxDB. The ease of installation and cluster creation were clear winners. Additionally the storage options for Influx trump Graphite across the board. I tried writing a custom backend and it went nowhere. The docs and code are terrible. I also noticed that Ceres hasn't had a commit in a year - kind of disheartening.
jmelloy 12y ago
Graphite's rendering functions are its real beauty. I looked at both OpenTSDB and InfluxDB as replacements, and neither have anything close to the power of Graphite's rendering. I haven't been thrilled with grafana as a dashboard for OpenTSDB, either. I hadn't seen Cyanite.
brunoqc 12y ago
Is there a workaround to get a moving average?

by Shish2k 12y ago

pauldix 12y ago

I think the tagging features in the upcoming 0.9.0 release [1] will help with the navigation of metrics. With that we're adding new types of queries to help in discovery. [2] [1] - http://influxdb.com/blog/2014/12/08/clustering_tags_and_enhancements_in_0_9_0.html http://influxdb.com/blog/2014/12/08/clustering_tags_and_enha... [2] - https://github.com/influxdb/influxdb/blob/master/QUERIES.md#list https://github.com/influxdb/influxdb/blob/master/QUERIES.md#...

the_vincedent 12y ago

Totally in the InfluxDB camp too. I've spent the last week working on upgrading our Graphite system. I ultimately killed it and went with InfluxDB. The ease of installation and cluster creation were clear winners. Additionally the storage options for Influx trump Graphite across the board. I tried writing a custom backend and it went nowhere. The docs and code are terrible. I also noticed that Ceres hasn't had a commit in a year - kind of disheartening.

jmelloy 12y ago

Graphite's rendering functions are its real beauty. I looked at both OpenTSDB and InfluxDB as replacements, and neither have anything close to the power of Graphite's rendering. I haven't been thrilled with grafana as a dashboard for OpenTSDB, either. I hadn't seen Cyanite.

brunoqc 12y ago

Is there a workaround to get a moving average?