Write data with no-code third-party technologies

A number of third-party technologies can be configured to send line protocol directly to InfluxDB.

If you’re using any of the following technologies, check out the handy links below to configure these technologies to write data to InfluxDB (no additional software to download or install):

Configure Vector

  1. View the Vector documentation:
  2. Under Configuration, click v2 to view configuration settings.
  3. Scroll down to How It Works for more detail:

Configure Apache NiFi

See the InfluxDB Processors for Apache NiFi Readme for details.

Configure OpenHAB

See the InfluxDB Persistence Readme for details.

Configure Apache JMeter

To configure Apache JMeter, complete the following steps in InfluxDB and JMeter.

In InfluxDB
  1. Find the name of your organization (needed to create a bucket and token).
  2. Create a bucket using the influx CLI and name it jmeter.
  3. Create a token.
In JMeter
  1. Create a Backend Listener using the InfluxDBBackendListenerClient implementation.
  2. In the Backend Listener implementation field, enter:
  3. Under Parameters, specify the following:
    • influxdbMetricsSender:
    • influxdbUrl: (include the bucket and org you created in InfluxDB)
    • application: InfluxDB2
    • influxdbToken: your InfluxDB API token
    • Include additional parameters as needed.
  4. Click Add to add the InfluxDBBackendListenerClient implementation.

Configure FluentD

See the influxdb-plugin-fluent Readme for details.

Was this page helpful?

Thank you for your feedback!

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

InfluxDB Cloud powered by TSM