i-ky
InfluxDB 3.0 support
I don't expect this to get worked on but I'll throw it up here anyways.
Hi @mfreeman451, thank you for filing this request!
At a glance InfluxDB 3.0 seems to use API v2 brought by InfluxDB 2.0 (in which case this issue is a duplicate of #11). Is it true or did I miss something?
InfluxDB 3.0 is a complete rewrite, some of the older stuff might be backward compatible but if we're going to be building something new, this would not be a duplicate of #11
On Fri, Jan 5, 2024 at 1:36 AM i-ky @.***> wrote:
Hi @mfreeman451 https://github.com/mfreeman451, thank you for filing this request!
At a glance InfluxDB 3.0 seems to use API v2 brought by InfluxDB 2.0 (in which case this issue is a duplicate of #11 https://github.com/i-ky/effluence/issues/11). Is it true or did I miss something?
— Reply to this email directly, view it on GitHub https://github.com/i-ky/effluence/issues/19#issuecomment-1878250723, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAN4Z2Q6UKCK367PLJLPV7DYM6UQRAVCNFSM6AAAAABBNSIBKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZYGI2TANZSGM . You are receiving this because you were mentioned.Message ID: @.***>
It can be a total rewrite and still be compatible API-wise and protocol-wise.
Have you actually tried using the module with InfluxDB 3.0? Does it give any errors?
It wouldn't be something I would want to use, Influx is recommending to use the new API. Regardless the request for 2.0 support is still open so I don't see how that would help me at all..
On Fri, Jan 5, 2024 at 2:37 PM i-ky @.***> wrote:
It can be a total rewrite and still be compatible API-wise and protocol-wise.
Have you actually tried using the module with InfluxDB 3.0? Does it give any errors?
— Reply to this email directly, view it on GitHub https://github.com/i-ky/effluence/issues/19#issuecomment-1879229381, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAN4Z2T3P3CIZOCXEBTSJ4LYNBP7VAVCNFSM6AAAAABBNSIBKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZZGIZDSMZYGE . You are receiving this because you were mentioned.Message ID: @.***>
I've started to give this project a bit of a facelift, but since I don't use it myself, this activity has a very low priority. I would consider raising priority, if there are any reports of things that are actually broken with InfluxDB 2.0/3.0.
I will start by configuring Gitpod-based development environment, so that it is easy to spin up a test environment with both InfluxDB and Zabbix (and probably with Grafana as well).
After that I will look into changes in the API.
@tharikahmad, @tanonl, I have noticed that you have changes related to InfluxDB 2.7 support in your forks (https://github.com/tharikahmad/effluence and https://github.com/v2cloud/effluence). I will be very happy to receive a PR from you. Or, at least, please share your experience with InfluxDB 2.x.