The Influx team is doing great things - however from the perspective of someone who's tried using InfluxDB in the last few months for a production app:<p>I really, really wish they'd hire 2-3 more database engineers to focus on the actual timeseries database, not nice looking tooling around it.<p>Simple things like incremental backups are still not working as expected in recent releases. Useful features from the 0.8 series still haven't been ported. And tsm1 is a neverending effort it seems.<p>We've went back to Postgres for storing timeseries data since we didn't feel confident to use InfluxDB in production.
I have been using InfluxDB (for throwing data into) and Grafana (for displaying pretty charts of that data). It's pretty great.<p>I had no idea InfluxData forked Grafana and developed their own (currently closed-source) visualization tool named Chronograf. It looks like a InfluxData branded version of Grafana. Also interesting is that it's the only closed-source element of their TICK stack.<p>Seems like there could easily be a conflict of interest here, such as new features of InfluxData only working with Chronograf and not Grafana.<p>grafana - <a href="http://grafana.org/" rel="nofollow">http://grafana.org/</a><p>chronograf - <a href="https://influxdata.com/get-started/#visualizing-data-with-chronograf" rel="nofollow">https://influxdata.com/get-started/#visualizing-data-with-ch...</a>
Good to see the forward progress. I needed to set up a metrics platform to serve tenants on a Mesos cluster, and picked InfluxDB over some alternatives for 3 main reasons: fairly reliable working state at the time (still using 0.8.8) with no dependencies, upward momentum, and stated priority of horizonal scaling. Looking back, it's held up reasonably well. I'm admittedly disappointed that stable, horizontally-scalable clustering keeps getting pushed to the next release. To be fair, it's hard, and the redisigns with the 0.9+ API and TSM tree are important - if you're going to sell people on a dedicated time series DB it has to be really really good at it.<p>In the long run, the full ecosystem development here will pay off.
It's interesting to see some competition in this space.<p>Basho, the maker of Riak has also moved from being a db company to being a data platform company. And they've also launched a time series version of Riak.
First, I really like the rebrand and wider focus. I think it will help people understand how your suite of tools work together (I just started playing with InfluxDB + Go yesterday and am loving it, and Telegraf seems a natural fit for another upcoming project too).<p>There's a lot of mention about the ephemeral nature of time series data, but how is InfluxDB for storing permanent time series data? Are there any performance limitations I should be thinking about (aside from the limits of the hardware itself)?
Their stack is starting to look good, at least on paper.<p>I'm particularly interested in Telegraf. We're using Prometheus for data collection and monitoring right now, and collection system is definitely the weakest part.
I'm a fan. Chronograf looks like an interesting alternative to Grafana - but it's not open source :( Kapacitor looks neat as well, though it's going up against stiff competition from Bosun.