4 ms·
I also dropped InfluxDB at work due to its terrible performance. VictoriaMetrics is great I was using Promscale (TimescaleDB) but they EOL'd Promscale which fo
by keep_reading 3y ago
I also dropped InfluxDB at work due to its terrible performance. VictoriaMetrics is great
I was using Promscale (TimescaleDB) but they EOL'd Promscale which forced us to Victoria. But either way both of these are much faster than Influx
Don't get fooled into the latest InfluxDB rewrite. I think the latest is cloud hosted only too? So stupid
- pphysch 3y agoI saw the writing on the wall with InfluxDB v2 (doubling down on closed platform / SaaS) and advocated exploring VictoriaMetrics, even though we had some Influx v1 running. No regrets. I also prefer the golang-esque simplicity of the Prometheus ecosystem. Monitoring is the last place I want unnecessary abstraction layers and complicated configuration files.
- contravariant 3y agoHonestly the database isn't half as useful as the tool they wrote to grab the metrics. At least I think telegraf was written by the same people? It seems to have the exact opposite design philosophy.
- heipei 3y agoYup, telegraf is what keeps me with InfluxDB, even if I couldn't care less about the database or the pain in the ass it is to operate.
- contravariant 3y agoVictoriaMetrics does claim to be compatible with the inline format, which makes me wonder if it is possible to keep using telegraf with it.
- keep_reading 3y agoYou can. I also use Telegraf with TimescaleDB. Telegraf actually made interop with their competitors super easy
- somedude82 3y agoInfluxData is killing InfluxDB with their changes. Their v1->v2->v3 changes are beyong insane. They revealed that flux is deprecated in v3, their main selling point for v2. In database domain you would like stability not breaking change in every 2-3 years. See https://news.ycombinator.com/item?id=37206194 https://news.ycombinator.com/item?id=37206194
- networkchad 3y ago[dead]