- 162
- 45
- NAS
- DS918+ (8GB RAM, 4x WD RED 4TB SHR) ; EATON Ellipse PRO 1200FR
- Operating system
- Windows
- Mobile operating system
- Android
Well pointed, I was looking for this kind of information before pulling the trigger on influx 2.0... For now I'll stick with influx 1.8.Influxdb 2.x uses the query language "Flux", while Influxdb 1.x uses the query language "InfluxQL". The two query languages are completly differet and existing InfluxQL queries need to be migrated to Flux queries.
I tested it yesterday while turning Rusty's blogpost into a docker-compose.yml. It was quite straight forward, except when it came to register the InfluxDB in Grafana and of course the surprise when I imported prexisting dashboards and figured none of them actualy uses Flux queries under the hood. A dashboard usualy has many panels, each panal has one or more metrics.. each query needs to be migrated from InfluxQL to Flux to make it work.
Thus said, for the sake of comfort I would advice to stay with inflxdb 1.x for time![]()
Also migrated my GIT to a stack in portainer (adapting my commandline to fit in compose)