Documentation

Telegraf

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!

© 2025 InfluxData, Inc.

Where are you running InfluxDB?

Select your InfluxDB Cloud region and cluster or your InfluxDB OSS URL and we’ll customize code examples for you. Identify your InfluxDB Cloud cluster.

  • InfluxDB Cloud
  • InfluxDB OSS or Enterprise
AWS

  • US West (Oregon)

GCP
Azure
Default
Custom

For more information, see InfluxDB Cloud regions or InfluxDB OSS URLs.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, 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