-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to support InfluxDB 2.0 #45
Comments
As I know influxdb 2.0 will still support InfluxQA as now, so what would be the needed change? |
I'm using an InfluxDB for sensor applications and experimentally set up
an InfluxDB 2.0 server for testing / using Flux protocol
My iobroker was not able to connect to this server, so I cannot store
data and test it. Maybe the problem is with my setting and you can help
me to connect?
…------ Originalnachricht ------
Von: "Ingo Fischer" <notifications@github.com>
An: "ioBroker/ioBroker.influxdb" <ioBroker.influxdb@noreply.github.com>
Cc: "jomjol" <mueller.josef@gmail.com>; "Author"
<author@noreply.github.com>
Gesendet: 16.04.2019 10:57:45
Betreff: Re: [ioBroker/ioBroker.influxdb] Upgrade to support InfluxDB
2.0 (#45)
As I know influxdb 2.0 will still support InfluxQA as now, so what
would be the needed change?
OR do you say we need to switch to use Flux protocol?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#45 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AdV1x7yDB35LyBIcNuFT7aUMeEBTLEU8ks5vhZCJgaJpZM4cxtCF>.
|
When I understand https://github.com/influxdata/influxdb correctly the the Influx 1.x compat layer is still "planned" and so not implemented right now ... so ay to early :-) |
BTW: The adapter is relaying on https://github.com/node-influx/node-influx to be updated to be 2.0 compatible ... so first an issue there would be any idea, but projects somehow seems not that active :-( |
Thanks a lot. I keep an eye on that.
…------ Originalnachricht ------
Von: "Ingo Fischer" <notifications@github.com>
An: "ioBroker/ioBroker.influxdb" <ioBroker.influxdb@noreply.github.com>
Cc: "jomjol" <mueller.josef@gmail.com>; "Author"
<author@noreply.github.com>
Gesendet: 16.04.2019 12:35:53
Betreff: Re: [ioBroker/ioBroker.influxdb] Upgrade to support InfluxDB
2.0 (#45)
BTW: The adapter is relaying on
https://github.com/node-influx/node-influx to be updated to be 2.0
compatible ... so first an issue there would be any idea, but projects
somehow seems not that active
:-(
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#45 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AdV1x3Gcqu7WS8SU9DCm_PCXOLClu68_ks5vhaeJgaJpZM4cxtCF>.
|
There are no plans to support Influx v2 by node-influx node-influx/node-influx#483 |
Thank you for linking ... so means that we might need to migrate over to https://github.com/influxdata/influxdb-client-js/ ... So means: 1. modularize code so that user can select the influxdb version |
Is anyone currently working on this? |
No, influxdb2 will get a v1 api compatibility layer so in a first place it is not that needed and changing over to a new library will be a bigger effort as it seems because it should also contain "thinking about better data structure" and such. And noone had time for this so far. Why you ask? We are also interested in PRs :-) |
Deleting mv v2 instance (though I liked it better) and will stick with 1.8 for now... PR - if my dev skills would extend to node; maybe some other time ;). |
Tested today with the influxDB 2.0 RC. Authentication works using a token as password; The adapter does not initialize, as the "show databases" command is not supported by the API compatibility layer (only /read and /write are, see https://docs.influxdata.com/influxdb/v2.0/reference/api/influxdb-1x/). |
Hm ... we could add a way to ignore DB creation and manually show the commands to create dbs or such ... ?! |
@savek-cc can you please post a log from a start with influxdb 2? |
That log doesn't really say much on its own I guess. |
savek-cc commented on 28 Oct 2020: "Authentication works using a token as password" Does this mean you have been able to connect to your installation using the iobroker adapter? Tried it with Influx Version Version 2.0.4 (4e7a59b) but got "(146990) Error: {"code":"unauthorized","message":"Unauthorized"}" Are there any further updates on implementations / ideas / workarounds to get data into influxdb 2? Or is it maybe even better to find another way (database) to make iobroker data available in Grafana? Many thanks. Cheers! |
@LePremier it's been a while since I tried, but I am somewhat (quite?) certain that it was authorized. Only after that authentication it failed with invalid commands afaict. |
Hm, ok. Even the first step doesn't seem to work in my setup. Anyways, @savek-cc have you found another way to get your iobroker data be stored in an external DB (and be visualized in Grafana)? E.g. by using another data base, like mySQL with the ioBroker SQL Adapter? @Apollon77 et al.: Are there any further updates on implementations / ideas / workarounds to get data into influxdb 2? Or can you recommend something else? Many thanks! |
In fact from my side we could add a flag that is bypassing then the "db initialization" because we know that at least sending data works via the compatibility layer. No idea about the kind of selections we do. For this to work for new users of the adapter we need to add a guide on how to create the relevant stuff for influxdb by themself (the "database and tables and such"). Then we could have a "veeeery basic compatibility thing" working. A real support will rewriting the whole data management in teh adapter to use a influxdb 2 library ... This is a bigger thing and mainly needs time. It is on my list, but otehr stuff is on top if it. Till now no other dev was found to take on that |
Thanks @Apollon77. Having the mentioned "very basic compatibility thing" working would be a great short term workaround. Would be great if you could provide the required details. I would than try to do the setup based on that. While doing so I could do some screenshots and notes that can be used for a more detailed documentation afterwards? I also would love to support you with a more sustainable rewrite of the adapter, but unfortunately I think my programming skills are not yet advanced enough :( ... But please let me know if I can support the project in another way (e.g. collecting required information, etc.) |
This topic is currently in development and we might have a testversion soon that can then support influxdb 1.8 and 2.x. Stay tuned, we then need testers :-) |
I am in! 😃 ... really great news. Many thanks for your efforts. |
great to hear! |
Very nice, many thanks!!!!! |
I hope I find time till latest weekend to check the PR and prepare a testing version |
Is there any news about the current status? What about the pull request that is supposed to support InfluxDB2.0? |
Yes, still on list, hopefully soon. Was bound in private live to an other topic ... |
I'm really curious about this update as well :-D. Hope to see it soon |
Ok gyus, lets go ... Tests started --> https://forum.iobroker.net/topic/46098/test-adapter-influxdb-2-0 |
Adapter 2.1.1 officially released just now |
Support to connect to InfluxDB 2.0:
https://www.influxdata.com/blog/influxdb-2-0-alpha-release-and-the-road-ahead/
Although still in the Alpha state, the 2.0 version support enhanced DB management tools (e.g. Influx language to further process input data).
The text was updated successfully, but these errors were encountered: