[kawsper]

Grafana really looks interesting, and it is interesting that you can add all the different backends to it, for an example I didn't know you can use Elasticsearch as a timeseries backend.

Is it correct that Grafana works best with Graphite? At least that seems to be my impression, and it is a bit sad, since I think Graphite is cool, but it really has a lot of moving parts.

[pfranz]

I wouldn't let that stop you from evaluating it. At my last few jobs I've used Grafana with Elasticsearch and Prometheus without a problem. I've never actually used it with Graphite. The only downside I've seen is that the queries are unique to the data source, so when looking at many of the examples online you have to figure out the equivalent for your's. There might be a performance difference, but I wouldn't know it since I haven't used Graphite.

[gtrubetskoy]

We use it with Tgres [1] (which only pretends to be Graphite, but actually is Golang + PostgreSQL) - works great.

[1] https://github.com/tgres/tgres

[pimeys]

Using it with InfluxDB, Prometheus and Zabbix. Works like a charm. One of my favorite tools!

[mattttt]

Graphite was the original, but as others have mentioned, Influx, Prom, Cloudwatch & Elasticsearch are all first-class data sources.

[beachy]

We use it with influx, works great, though I find influx's syntax to be funky.

We also use it against mysql. Annoyingly there is no driver for that so we had to build a nasty layer than translates from influx to mysql.

[mkching]

Today after fighting with Kibana all morning, I decided to tweak our scripts to build Grafana dashboards against our existing ElasticSearch data store. Very fast to get up and running and the the features and speed are amazing.

Very glad I saw this announcement on HN.

[jmedefind]

I've used it with Influxdb, Elasticsearch, and Prometheus.

They all worked great. I can't think of any reason to use Graphite.

[regecks]

Indeed. We reduced our write iops by 95% by moving from Graphite/Carbon to Influx. Try one of the newer databases!