Documentation

Use the Plugin Library

The InfluxDB Plugin Library is a collection of pre-built InfluxDB 3 plugins that you can install in your InfluxDB 3 server. To view the Plugin library, navigate to Manage Plugins > Plugin Library in the left sidebar.

Search the Plugin Library

To search for plugins in the Plugin library, submit a search term in the search bar.

Install a plugin

  1. In the Plugin Library, locate the plugin you want to install.

  2. Click on the plugin card to open its details.

  3. To install a plugin from InfluxDB 3 Explorer select Install Plugin:

  4. Provide the following:

    • Database: Select the InfluxDB 3 database to associate the plugin with.

    • Trigger Name: A unique name for the plugin and trigger combination.

    • Trigger Type: Select the trigger type. What trigger types are available depend on the plugin.

      For more information about InfluxDB 3 plugin triggers, see Understand trigger types.

      Depending on the selected trigger type, provide the following:

      • Data Writes (All Tables): no additional configuration options.

      • Data Writes (Single Table):

        • Table Name: The name of the table that, when written to, triggers the plugin to run.
      • Schedule:

        • Frequency: When to run the plugin using one of the following patterns:
          • every:<duration>: Run at specified intervals–for example: every:15m.
          • cron:<cron-expression>: Run on a cron schedule–for example: cron:0 */12 * * *.
      • HTTP Endpoint:

        • API Endpoint: The API endpoint name to use to trigger the plugin–for example: downsample. To trigger the plugin, you would then send a request to the /api/v3/engine/downsample endpoint of your InfluxDB server to trigger the plugin.
      • Advanced Settings

        • Run Asynchronously: Execute the plugin asynchronously and do not wait for a response.
        • Error Behavior: Specify the action you want the plugin to take when it encounters an error:
          • Log: Log the error to your InfluxDB server’s logs.
          • Retry: Retry the plugin execution.
          • Disable: Disable the plugin.
      • Arguments: Specific arguments to pass to the Plugin. Plugins can have both required and optional arguments.

  5. Click Deploy to install the plugin.

Other plugin installation options

InfluxDB 3 Explorer also lets you do the following:

  • Download Code: Download the plugin code to view it or modify it for your own use.
  • Copy Install Command: Copy the influxdb3 CLI command you can use to manually install the plugin on your InfluxDB 3 server.

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