Hello. I just started integrating FluxDB 2 as a time series data base. And I noticed that the Grafana query editor is not as good as for Influx 1. On the other hand version 1 is deprecated. And it seems that 2 is also more or less deprecated because the company focuses on version 3, which is not open source. So the question: Which DB to use? Is there a new default? May be VictoriaMetrics? Or is this topic uncertain?
#Which time series DB?
terse dagger
midnight comet
I think VictoriaMetrics is a great choice and I use it myself. It supports influx and prometheus and others and uses prometheus inspired syntax that to me is much easier to understand than influx one's. Influx DB 2 is much more popular though and you likely get better support due to that.
vocal cairn
Too bad downsampling is an enterprise feature of VM. Would love to switch from InfluxDB.
midnight comet
Yeah it's sad but it's extremely space efficient. It's not so bad without.
vocal cairn
Although, implementing in Influx has been on my todo list for 5+ years, still have full multi-second metrics for many temperature sensors and its been pretty solid. Probably could switch w/o issue. Influx v1.11 was just released, so it's not technically dead yet.
violet eagle
I've been using timescale at work, if I was doing it over that's the direction I'd go
sinful flame
Hi Sascha,
i use InfluxDB v2 very intensivly at work and home ... query language on v2 (flux) is not easy to learn an the builder is not so flexible ... once you learned this language you will find that InfluxDB is very flexible and fast. There is a new version on the way InfluxDB v3 this will keep the flux language but will revert to fluxQL that is similar to what was used in InfluxDB v1 and is an SQL analog language.
Prometheus is maybe also something that you should give an try but remeber that Prometheus have problems with string manipulation...
I think you need an "data source" for Grafana or similar 🙂 ....
Gerhard