it might be useful to announce the v2 api support more explicitly

[jubalfh]

Hey,

So this is not an issue per se, just something that might be helpful for other people considering influx 2.0, and the route of the home-made influx clustering – and slowly realising that influx' own unloved influxdb-relay is now finally properly dead, then finding the veepee's fork, going through the issues and realising that it doesn't look like that the fork will ever support v2 api, and after additional googling finding your repos, and getting ready for disappointment only to find that the v2 api support PR was successfully merged a few months ago.

Also, thanks for your hard work. There's a huge gap between single-node influx installations and needing full-blown enterprise package, and this project fills it very well.

[jcdauchy-moodys]

I don't think I understand what you mean ? Have you tested and feedback for influx v2 ? I am using srelay and syncflux for 2 years now on 3 master -> slaves clusters, it seems to work fine (even with Flux support). It would be nice to have influxdb v2 but I don't want to screw up all my work as I don't see what I need in v2.

[toni-moreno]

Hello @jcdauchy-moody's is nice to hear about successfully use cases for the tuple influxdb-srelay/syncflux tools.

Could you please share with us your use case, which context/business, data volumetry in your clusters, influxdb version, and maybe (only if you can) the name of your company which is taking advantage for these completely open-source and free tools?

Thank you in advance!