Documentation

influxdb3 show plugins

The influxdb3 show plugins command lists loaded Processing Engine plugins in your InfluxDB 3 Enterprise server.

Usage

influxdb3 show plugins [OPTIONS]

Options

OptionDescription
-H--hostHost URL of the running InfluxDB 3 Enterprise server (default is http://127.0.0.1:8181)
--token(Required) Authentication token
--formatOutput format (pretty (default), json, jsonl, csv, or parquet)
--outputPath where to save output when using the parquet format
--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_AUTH_TOKEN--token
INFLUXDB3_TLS_NO_VERIFY--tls-no-verify

Output

The command returns information about loaded plugin files:

  • plugin_name: Name of a trigger using this plugin
  • file_name: Plugin filename
  • file_path: Full server path to the plugin file
  • size_bytes: File size in bytes
  • last_modified: Last modification timestamp (milliseconds since epoch)

This command queries the system.plugin_files table in the _internal database. For more advanced queries and filtering, see Query system data.

Examples

List all plugins

influxdb3 show plugins

List plugins in different output formats

You can specify the output format using the --format option:

# JSON format
influxdb3 show plugins --format json

# JSON Lines format
influxdb3 show plugins --format jsonl

# CSV format
influxdb3 show plugins --format csv

Output plugins to a Parquet file

Parquet is a binary format. Use the --output option to specify the file where you want to save the Parquet data.

influxdb3 show plugins \
  --format parquet \
  --output /Users/me/plugins.parquet

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