Documentation

influxdb3 test wal_plugin

The influxdb3 test wal_plugin command tests a write-ahead log (WAL) plugin.

Usage

influxdb3 test wal_plugin [OPTIONS] --database <DATABASE_NAME> <PLUGIN_NAME>

Arguments

  • PLUGIN_NAME: The name of the plugin file on the server–for example: <plugin-dir>/<plugin-file-name>.py

Options

OptionDescription
-H--hostHost URL of the running InfluxDB 3 Core server (default is http://127.0.0.1:8181)
-d--database(Required) Name of the database to operate on
--token(Required) Authentication token
--lpLine protocol to use as input
--fileLine protocol file to use as input
--input-argumentsMap of string key-value pairs as to use as plugin input arguments
--tls-caPath to a custom TLS certificate authority (for testing or self-signed certificates)
--tls-no-verifyDisable TLS certificate verification (Not recommended in production, useful for self-signed certificates)
-h--helpPrint help information
--help-allPrint detailed help information

Option environment variables

You can use the following environment variables to set command options:

Environment VariableOption
INFLUXDB3_HOST_URL--host
INFLUXDB3_DATABASE_NAME--database
INFLUXDB3_AUTH_TOKEN--token
INFLUXDB3_TLS_NO_VERIFY--tls-no-verify

Examples

In the examples below, replace the following:

  • DATABASE_NAME: Database name
  • AUTH_TOKEN: Authentication token
  • PLUGIN_DIR: Plugin directory name
  • PLUGIN_NAME: Plugin file name

Test a WAL plugin

influxdb3 test wal_plugin \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
PLUGIN_DIR
/
PLUGIN_NAME
.py

Test a WAL plugin with a line protocol string

influxdb3 test wal_plugin \
  --lp 'home,room=Kitchen temp=21.0,hum=35.9,co=0i' \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
PLUGIN_DIR
/
PLUGIN_NAME
.py

Test a WAL plugin with a file containing line protocol

influxdb3 test wal_plugin \
  --file 
PLUGIN_DIR
/
PLUGIN_NAME
_test/input-file.lp`
--database
DATABASE_NAME
\
--token
AUTH_TOKEN
\
PLUGIN_DIR
/
PLUGIN_NAME
.py

Test a WAL plugin using input arguments

influxdb3 test wal_plugin \
  --input-arguments arg1=foo,arg2=baz \
  --database 
DATABASE_NAME
\
--token
AUTH_TOKEN
\
PLUGIN_DIR
/
PLUGIN_NAME
.py

Was this page helpful?

Thank you for your feedback!


InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

Telegraf Controller v0.0.6-beta now available

Telegraf Controller v0.0.6-beta is now available with new features, improvements, and bug fixes.

View the release notes
Download Telegraf Controller v0.0.6-beta

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2