Telegraf to accept tokens on v1 InfluxDB input plugins - Githubissues

influxdata / telegraf

Agent for collecting, processing, aggregating, and writing metrics, logs, and other arbitrary data.

https://influxdata.com/telegraf

MIT License

14.63k stars 5.58k forks source link

Telegraf to accept tokens on v1 InfluxDB input plugins #9445

Closed sjwang90 closed 1 year ago

sjwang90 commented 3 years ago

Feature Request

Opening a feature request kicks off a discussion.

Proposal:

Add tokens (alongside existing username/password) to the InfluxDB Listener v1 plugin.

Use telegraf as an aggregator in front of the Cloud 2 API with v1 capability.
Even though v2 listener https://docs.influxdata.com/telegraf/v1.18/plugins/#influxdb_v2_listener exists, I was hoping the inputs.influxdb_listener would provide similarly a “fake” v2 with token = user:password (just like InfluxDB 1.8) on the same port as the regular v1 API (the v2 listener I think would require a different port).

Current behavior:

Telegraf InfluxDB Listener v1 input plugin only supports username/password not tokens.

Desired behavior:

Allow for token configuration in inputs.influxdb_listener. The token would just be what’s listed in compatibility API: https://docs.influxdata.com/influxdb/v2.0/reference/api/influxdb-1x/#basic-authentication

Use case:

Make migration experience from 1.x to 2.x more seamless.

For example, while using the Go library (https://github.com/influxdata/influxdb-client-go#influxdb-18-api-compatibility) and noticed it didn't work with Telegraf.

sjwang90 commented 3 years ago

We will implement this feature work as part of the initiative in #9478 issue to combine v1/v2 plugins and make sure any influxdb has compatibility with both versions.