[Question Only] Is it usable with InfluxDB 2.0 about influxdb-php

[bednar]

Hi @jadamroth,

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

Regards

[rawkode]

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

[andig]

Same question here?

[rawkode]

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]

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

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

[andig]

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]

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

[rawkode]

Example in this issue:

influxdata/telegraf#809

[andig]

Example in this issue: influxdata/telegraf#809

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

[andig]

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]

Is there any update on InfluxDB 2.0 compatibility?

[jadamroth]

Hey @rawkode , any updates on timeline?