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!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: