Skip to content
This repository has been archived by the owner on Nov 15, 2022. It is now read-only.

[Question Only] Is it usable with InfluxDB 2.0 #139

Open
CatsPlugins opened this issue Oct 17, 2019 · 12 comments
Open

[Question Only] Is it usable with InfluxDB 2.0 #139

CatsPlugins opened this issue Oct 17, 2019 · 12 comments

Comments

@CatsPlugins
Copy link

Hello,

I'm using InfluxDB 1.7 with this PHP SDK, and it's working fine.

I want to upgrade to InfluxDB 2.0, so will it work with v2?

Thank you!

@andig
Copy link
Contributor

andig commented Oct 28, 2019

Same question here?

@rawkode
Copy link

rawkode commented Oct 28, 2019

No, it won't work; though work has begun on a client for 2.x. Please bare with us. I'll keep this issue updated over the coming days and weeks.

@rawkode
Copy link

rawkode commented Oct 28, 2019

I'm the interim, we suggest using Telegraf as a proxy.

https://www.influxdata.com/blog/influxdb-2-migration-path-instrumentation/

@andig
Copy link
Contributor

andig commented Oct 28, 2019

I'm the interim, we suggest using Telegraf as a proxy.

This is a little offtopic, please advise if there's a better place to ask. The link above suggests to use Telegraf for relaying. Thats good to know!

However, I already have outputs.influxdb_v2 enabled for purpose of sending metrics to a metrics bucked. If I need to use it for inputs.influxdb -> outputs.influxdb_v2 relay too, then it would need to go to a different bucket. How would I separate these two?

@rawkode
Copy link

rawkode commented Oct 28, 2019

You'd need to use the namepass/namedrop parameters on your 2 different InfluxDB outputs, or use a separate instance of Telegraf

@rawkode
Copy link

rawkode commented Oct 28, 2019

Example in this issue:

influxdata/telegraf#809

@andig
Copy link
Contributor

andig commented Oct 29, 2019

Example in this issue: influxdata/telegraf#809

Thank you! Joined influxdata/telegraf#1778 which seems to have a more detailed discussion.

@andig
Copy link
Contributor

andig commented Oct 29, 2019

Unfortunately, as the docs say:

This plugin allows Telegraf to provide an InfluxDB 1 /write compatible proxy. This will not allow you to read from InfluxDB, should you be using any of the client libraries for that purpose.

As I'm periodically copying from another DB to influx (v1 at the moment) and need to know the last point written (i.e. do a query) that won't work :/

@jadamroth
Copy link

Is there any update on InfluxDB 2.0 compatibility?

@rawkode
Copy link

rawkode commented Jan 13, 2020

@jadamroth No, not at the moment. With our recent beta announcement, this will change very soon 👍

@jadamroth
Copy link

Hey @rawkode , any updates on timeline?

@bednar
Copy link
Contributor

bednar commented Feb 21, 2020

Hi @jadamroth,

we started working on influxdb-client-php for InfluxDB 2... first results coming soon

Regards

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants