Documentation

Write an external plugin

Set up your plugin to use it with execd.

For listed external plugins, the author of the external plugin is also responsible for the maintenance and feature development of external plugins.

  1. Write your Telegraf plugin. Follow InfluxData’s best practices:
  2. If your plugin is written in Go, follow the steps for the Execd Go Shim.
  3. Add usage and development instructions in the homepage of your repository for running your plugin with its respective execd plugin. Refer to openvpn and awsalarms for examples. Include the following steps:
    • How to download the release package for your platform or how to clone the binary for your external plugin
    • Commands to build your binary
    • Location to edit your telegraf.conf
    • Configuration to run your external plugin with inputs.execd, processors.execd or outputs.execd
  4. Submit your plugin by opening a PR to add your external plugin to the /EXTERNAL_PLUGINS.md list. Include the plugin name, a link to the plugin repository and a short description of the plugin.

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