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 Core 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!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

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.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-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