We evaluated InfluxDB for our TSDB solution and found it to be generally high performance (up to about 100k unique series). Kapacitor also had some promising features for realtime aggregations, but was ultimately pretty buggy and didn't have support for out-of-order event processing. All in all, it looks like a great suite of products and we're curious to see how it evolves over the next few years.<p>Like many other users here, we were disappointed about paid clustering, but when the original press release said $400, we were willing to wait it out and see. However, we ultimately decided to go a different direction after seeing they wanted $20k+ to run clustering on a 256GB node. We ingest 10s of millions of data points per day from IoT sensors, and expect our data size to far exceed that capacity.<p>That said, we plan to run our own Cassandra cluster w/ KairosDB (<a href="http://kairosdb.github.io/" rel="nofollow">http://kairosdb.github.io/</a>) acting as a read / write abstraction layer. It'll cost us about $11k to run the cluster for the year, with 3 nodes @300GB/ea., leveraging Cassandra's (free) and open source clustering, HA, and replication technology.
I have just shut down 95% of my collectd/graphite infrastructure after migrating it over to InfluxDB+telegraf+grafana. I'm loving it! Since shutting down collectd, system load and io wait time across my fleet has gone way down, and available CPU has gone way up.<p>Though I wouldn't say it was a smooth transition. I started with 0.8, IIRC, and while it worked ok it used an amazing amount of storage. 4GB for a year worth of graphite data blew up to 100GB for a month of InfluxDB.<p>I gave up on InfluxDB a few times during the process, but at 0.11 I tried it again and is has been pretty good. We are only putting the Telegraf data and one small service statistic in it, but the storage is pretty reasonable at 12GB for a few months of data. Querying and graphing the data with Grafana is great.<p>If you have tried it before 0.11, definitely try it again. The guys giving a Prometheus talk at PyCon were really down on InfluxDB, but they hadn't tried it for 6 months. I was like "Yeah, it was unusable then". I wanted to like Prometheus, but I just couldn't figure out how to feed my data into it.
Great news from influxdata. Though all of these features (clustering, monitoring, and data elxploration) could be released with standard edition. The start of InfluxDB looked very promising, not sure if people feel the same with the chosen marketing model.
I really like the influxdb interface -- reading and writing data are super simple, but in some recent testing I did, it really really hated high-cardinality data sets.<p><a href="https://docs.influxdata.com/influxdb/v0.10/guides/hardware_sizing/#when-do-i-need-more-ram" rel="nofollow">https://docs.influxdata.com/influxdb/v0.10/guides/hardware_s...</a><p>Show stopper if you're in the same boat that I am.