Documentation

Contribute to Telegraf

There are many ways to contribute to InfluxData open source products. Whether you want to report a bug, write a plugin, or answer support questions, the following sections will guide you through the process.

Open GitHub issues

File bug reports

  1. Search Telegraf GitHub issues for related issues that are open or have been fixed.
  2. If an issue does not already exist, create a new bug report issue.
  3. Include all the requested details.

Do not open general support requests as GitHub issues. Support-related questions should be directed to the InfluxDB Community Slack or InfluxData Community forum.

Open feature requests

Feature requests help to prioritize work. To submit a feature request:

  1. Search Telegraf GitHub issues for issues related your feature request. Use the feature request label to filter issues by feature requests.
  2. If an issue related to your feature request already exists, indicate your support for that feature by using the thumbs up reaction and add a comment explaining your use case for the feature.
  3. If a feature request does not already exist, create a new feature request issue. Include the following with your feature request
  4. Include all the requested details.

Ask or answer support questions

Post support questions to InfluxDB Community Slack or InfluxData Community forum.

Contribute code

Create a pull request

  1. Sign the InfluxData CLA.

  2. Open a new issue to discuss the changes you would like to make. This is not strictly required, but it may help reduce the amount of rework you need to do later.

  3. Make changes or write plugins using the following plugin guidelines:

  4. Include unit tests and documentation for your change.

  5. Open a new pull request. The pull request title needs to follow the conventional commit format.

If you have a pull request with only one commit, the commit message must follow the conventional commit format, otherwise the Semantic Pull Request check will fail. For single-commit pull requests, GitHub uses the commit message as the default pull request title.

Contribute an external plugin

Input, output, and processor plugins written for Telegraf can be run as externally-compiled plugins through the execd input, execd output, and execd processor plugins without having to change the plugin code.

For more information, see:

  • Execd Go Shim: Use the Go execd shim to compile your plugin as a separate app and run it with the respective execd plugin.
  • Write an external plugin: Build and set up external plugins to run with execd.

Report security vulnerabilities

InfluxData takes security and our users’ trust very seriously. If you believe you have found a security issue in any of our open source projects, please responsibly disclose it by contacting security@influxdata.com. For more information about reporting security vulnerabilities, including our GPG key, see How to report security vulnerabilities.


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: