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!


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.8

Explorer 1.8 is now available with streaming data subscriptions (beta), line protocol preview, and query history & saved queries.

View Explorer 1.8 release notes

Explorer 1.8 includes new features and improvements that make it easier to ingest, explore, and manage data.

Highlights:

  • Streaming data subscriptions (beta): Stream data into Explorer from MQTT, Kafka, and AMQP sources.
  • Line protocol preview: Preview line protocol, schema, and parse errors before data is written.
  • Custom sample data: Generate custom sample datasets with line protocol and schema preview.
  • Query history and saved queries: Browse query history and save/re-run named queries.
  • Retention period management: Set, update, or clear retention periods on databases and tables.

For more details, see Explorer 1.8 release notes

InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

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:

Telegraf Controller v0.0.7-beta now available

Telegraf Controller v0.0.7-beta is now available with new features, improvements, bug fixes, and an important breaking change.

View the release notes
Download Telegraf Controller v0.0.7-beta

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