-
-
Notifications
You must be signed in to change notification settings - Fork 137
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
[Feature Request] Support for InfluxDB 2.0 #159
Comments
An alternative option would, of course, be to use an InfluxDB instance specifically for Varken. How intended is it to use your own, general InfluxDB account vs using one specifically for Varken? |
Will always take a look at PRs! |
Any update regarding this feature? |
@afriberg It's an insane amount of work, so isn't going to happen any time soon (tm) |
After doing some research it looks like we will have to rewrite the DB module to use this project instead. https://github.com/influxdata/influxdb-client-python |
Hi, it would be nice if anyone could merge the pull request, so that we can start using influxdb2 with Varken. |
@Nicras I have not had the time to walk through this MR. I will try to make it a priority this evening. |
@dirtycajunrice I guess there were other things with higher priority that evening xD |
@dirtycajunrice bumping since this thread is getting old -- any news on getting @Nicras's pull request merged? Thanks a ton! |
Bumping again. Is there anything keeping Nicra's pull request from being merged? |
Yes, several things. We are contemplating only supporting certain modules that don't have off the shelf exporters which means a rewrite for 2.0 and parking the current version for 1.8.x only. If you direly need 2.0 support then you can run their fork for now. |
@samwiseg0 thanks for the update! I'll probably do that for the time being. |
As a workaround, you can create a old style db under a bucket and create user/pass for it. Get into influx CLI and get the list of buckets. If you dont have a bucket then create one. Use the bucket id to create a db Create a user/pass. This call will prompt you for a password Then use that info on the config
|
Tried to give this workaround a try and while it can connect fine it does some automation that crashes.
Maybe a config option to disable checking if database exists and creating a new database automatically? |
Is your feature request related to a problem? Please describe.
I want to use Varken with an instance of InfluxDB cloud, rather than using a locally hosted instance. This currently runs on version 2.0, and I expect that the project will want to connect to the newer version at some point in the future anyway.
Describe the solution you'd like
An option in the configuration to use the InfluxDB 2.0 API. The main difference I can see from the user side is that it uses api tokens rather than a username and password.
Describe alternatives you've considered
I've considered either hosting a 1.0 database myself, or copying the Radarr/Sonarr/Tautulli scripts from Varken and using them in my own project. However, I want to try to add support for the 2.0 client in Varken itself, if this is something you would want upstream.
The text was updated successfully, but these errors were encountered: