Documentation

influxdb3 test schedule_plugin

The influxdb3 test schedule_plugin command tests a schedule plugin. Use this command to verify plugin behavior without creating a trigger.

Usage

influxdb3 test schedule_plugin [OPTIONS] --database <DATABASE_NAME> <FILENAME>

Arguments

  • FILENAME: Path to the plugin file. Use the absolute path or the path relative to the current working directory, such as <plugin-dir>/<plugin-file-name>.py.

Options

OptionFlagDescription
-H--hostURL of the running InfluxDB 3 Enterprise server
(default: http://127.0.0.1:8181)
-d--database(Required) Name of the database you want to test the plugin against
--token(Required) Authentication token
--input-argumentsJSON map of key/value pairs to pass as plugin input arguments (for example, '{"key":"val"}')
--scheduleCron schedule to simulate when testing the plugin
(default: * * * * *)
--cache-nameOptional cache name to associate with the test
--tls-caPath to a custom TLS certificate authority for self-signed certs
--tls-no-verifyDisable TLS certificate verification (Not recommended in production, useful for self-signed certificates)
-h--helpShow basic help information
--help-allShow all available help options

Option environment variables

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

Environment VariableCorresponding Option
INFLUXDB3_HOST_URL--host
INFLUXDB3_DATABASE_NAME--database
INFLUXDB3_AUTH_TOKEN--token
INFLUXDB3_TLS_CA--tls-ca
INFLUXDB3_TLS_NO_VERIFY--tls-no-verify

Examples

In the examples below, replace the following:

  • DATABASE_NAME: Your target database
  • AUTH_TOKEN: Your authentication token
  • PLUGIN_DIR: the path to the plugin directory you provided when starting the server
  • FILENAME: Plugin file name

Test a schedule plugin

influxdb3 test schedule_plugin \
  --database 
DATABASE
_NAME \
--token
AUTH_TOKEN
\
PLUGIN_DIR
/
FILENAME
.py

Test with input arguments and a custom cron schedule

You can pass input arguments to your plugin as key-value pairs and specify a custom cron schedule (using Quartz cron syntax with six fields):

influxdb3 test schedule_plugin \
  --host http://localhost:8182 \
  --database 
DATABASE
_NAME \
--token
AUTH_TOKEN
\
--input-arguments threshold=10,unit=seconds \ --schedule "0 0 * * * ?" \
PLUGIN_DIR
/
FILENAME
.py
  • Pass plugin parameters using --input-arguments as comma-separated key=value pairs.
  • Use --schedule to set the plugin’s execution time with a Quartz cron expression. For example, “0 0 * * * ?” runs the plugin at the start of every hour.

Was this page helpful?

Thank you for your feedback!


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:

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