3 ms·
Not that it matters, but I would be happiest if you just picked up InfluxDB 1.8.x, Kapacitor, and Chronograf again. Really painful to see you guys abandon a gr
by exabrial 3y ago
Not that it matters, but I would be happiest if you just picked up InfluxDB 1.8.x, Kapacitor, and Chronograf again.
Really painful to see you guys abandon a great product lineup for the "we made our our programming language too!!!" hype train that was the hot thing 5-6 hypecycles ago. In the future, just stay off the hype wagon and stick to the core product.
The TICK stack was one of the coolest pieces of software developed and it is just unfortunate it was abandoned.
- pauldix 3y agoTelegraf is still very much alive and well. With v3, we realized the scope of what we were trying to do in v2 was simply too large. We're putting our focus back on the core of the database. Having an embedded VM (it'll be either Python or Javascript) will eliminate the need for Kapacitor in the stack, which had its own programming language and execution engine. Ultimately, we're trying to narrow the scope of what we're developing and letting other tools that people already know and use have first class placement in the InfluxDB stack.
- exabrial 3y agoWhat about Chronograf?
- pauldix 3y agoWe'll have to test Chronograf against 3.0, but I think it should just work. Unfortunately, we don't have the resources to continue developing it, but it's all available under a permissive MIT license here: https://github.com/influxdata/chronograf https://github.com/influxdata/chronograf
- exabrial 3y agoThat is unfortunate. You guys need to stop chasing shiny objects and pick up the 1.x stack. You had a lot going and you’re about to make the same mistakes again.