Documentation

Manage InfluxDB 3 plugins with InfluxDB 3 Explorer

InfluxDB 3 Explorer lets you manage plugins in your InfluxDB 3 instance or cluster. InfluxDB 3 Processing engine plugins let you extend your database with custom Python code. Use InfluxDB 3 Explorer to manage plugins in your InfluxDB 3 instance and install prebuilt plugins from the Plugin Library.

Each plugin can define one or more triggers—rules that specify when the plugin should execute. Triggers are typically based on conditions such as data arriving in a specific table or matching certain criteria.

  • Data writes - Process and transform data as it enters the database
  • Scheduled events - Run code at defined intervals or specific times
  • HTTP requests - Expose custom API endpoints that execute your code

When a trigger condition is met, InfluxDB 3 automatically runs the associated plugin code. This enables real-time data processing, enrichment, or alerting without manual intervention. Use the InfluxDB 3 Explorer UI to enable, disable, or configure triggers for each plugin.

View installed plugins

To view plugins installed in your InfluxDB 3 server, navigate to Manage Plugins > Overview.

  1. Navigate to the Manage Plugins > Overview section in the left sidebar.
  2. All installed plugins are listed under the All Plugins tab.

Filter installed plugins

To filter installed plugins by state, use the top tabs to filter by:

  • All Plugins
  • Running
  • Stopped
  • Errors

You can also use the search bar to filter by plugin name.

Enable or disable a plugin

  1. In the plugin list, locate the desired plugin.

    • If the plugin is currently running (enabled), click to disable the plugin.
    • If the plugin is currently stopped (disabled), click the button to enable the plugin.

View plugin logs

  1. In the plugin list, locate the desired plugin.
  2. Click Logs to view the most recent logs output by the plugin.
  3. To view more log entries, click View More.
  4. To export the logs, click Export.

Edit a plugin

  1. In the plugin list, locate the desired plugin.
  2. Click Edit.
  3. Edit the plugins settings.
  4. Click Save.

Editing a plugin removes and recreates the plugin

When editing an InfluxDB 3 plugin, InfluxDB 3 Explorer removes and recreates the plugin using the updated settings.

Delete a plugin

  1. In the plugin list, locate the desired plugin.
  2. Click the button to delete the plugin.
  3. Confirm that you want to delete the plugin.

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.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 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