Been using InfluxDB for a rather long time now and while I've had my share of the problems (including <a href="https://news.ycombinator.com/item?id=17768860" rel="nofollow">https://news.ycombinator.com/item?id=17768860</a>) generally I do like the ecosystem a lot. When it works it just works and it's awesome.<p>That said while TickScripts are not exactly a pleasure write, I wouldn't say a new language is pretty high on my wantlist. For example, as the blog post states:<p>> We also need to add features for backup & restore, bulk data import and export, and data deletes.<p>I'd take any of those over a new query language any day now. Especially the restore part is at the moment nearly completely non-existing after backup format change in InfluxDB, so good luck if you happen to run into data loss or just want to move around data in general. Same goes for data deletion outside of whole measurements.<p>I am hopeful that those features arrive before a 2.0 launch and hopefully in some sort of backwards compatible way (or at least ported to Influx 1.x).
Backup and easy restore (not having to run SQL statements to switch up tables) is the thing I care about the most.<p>I agree with the folks below suggesting you use javascript as the language instead of reinventing your own.
To other users of InfluxDB : How do you read data if you want to group, filter, sort by something other than time?<p>We used to use InfluxDB to store our perf data where every data point contained a timestamp (thus we thought influxdb was ideal for our use case). But, soon we wanted to group, filter, sort by various dimensions and it lead to performance issues.<p>Bringing it all in-mem and using pandas to do that was very slow for us. Also, creating indexes for so many columns didn't seem like a good idea.<p>We switched to postgres and the decision has served us well so far. I just want to understand if influx isn't suitable to our kind of use-case or we used it incorrectly.
> Kapacitor is the killer app<p>Um. Yes. Wait, there are people that use influxdb _without_ kapacitor alerting??? Someone name any commercial or open source equivalent, b/c I'd like to know in case they kill it.
I haven't seen flux and a few other things before, but it sounds really exciting. It looks like influx people release a lot of this info (and related tech like grafana) on their YouTube channel: <a href="https://www.youtube.com/channel/UCnrgOD6G0y0_rcubQuICpTQ" rel="nofollow">https://www.youtube.com/channel/UCnrgOD6G0y0_rcubQuICpTQ</a><p>Good content, it's a shame it's not more popular.
What's the story regarding high availability for InfluxDB 2.0? I know it is a commercial offering in the current release, and while I'm not super thrilled about that, I do think it's reasonable. It would be nice if you could buy the self-hosted version with a "contact sales" step which I honestly will never do. (I would just put a proxy in front of the multiple instances that tries to write to as many of them as possible and does reads from one at random. What could go wrong!)<p>The other thing I never figured out in the current version is how to write the following query. I store samples like (device, network, direction) -> packet count. I then want to know how many packets were sent across the network in total.<p>With monitoring systems I've used in the past (internal to my former employer), this was easy. You would do the delta calculation at the lowest level to convert device packet counters to number of packets sent in the last time interval, which varies randomly because samples are not necessarily arriving at discrete intervals. Then you would do an align, to bring the randomly-added sampling times into alignment across all the "streams" (which is a unique (device, network, direction)). Once the data is aligned, you can then do a group by to get rid of a certain tag, like device (and just have (network, direction) -> total packets sent in the time interval).<p>With InfluxDB, I can't figure out how to do this. It has the group by time concept, but not alignment, so I can't write a query that will work. I ended up just computing the deltas before inserting the item, at which point everything works fine.<p>I have not tried the same query with Prometheus, but I suspect it would work like I expect, as it seems very heavily inspired by a certain internal monitoring system I am most familiar with.