Documentation

Telegraf Plugin Documentation - Edit in Source Repository

The Telegraf plugin documentation in subdirectories (input-plugins/, output-plugins/, aggregator-plugins/, processor-plugins/) is generated from plugin READMEs in the influxdata/telegraf repository.

Workflow

  1. Source of truth: Plugin READMEs in telegraf/plugins/<type>/<plugin>/README.md
  2. Automated sync: The telegraf-internal repository generates documentation PRs from plugin READMEs
  3. Release process: Telegraf releases automatically trigger documentation updates

To Make Changes

  1. Edit the source README in the telegraf repository: plugins/<type>/<plugin>/README.md
  2. Submit a PR to influxdata/telegraf
  3. After merge, the sync process will create a PR to docs-v2

Plugin Types and Locations

DirectorySource Location
input-plugins/telegraf/plugins/inputs/<plugin>/README.md
output-plugins/telegraf/plugins/outputs/<plugin>/README.md
aggregator-plugins/telegraf/plugins/aggregators/<plugin>/README.md
processor-plugins/telegraf/plugins/processors/<plugin>/README.md

Documentation

  • Telegraf repository: https://github.com/influxdata/telegraf
  • Contributing guide: https://github.com/influxdata/telegraf/blob/master/CONTRIBUTING.md

Non-Generated Content

The following files in content/telegraf/ are not generated and can be edited directly:

  • _index.md
  • configuration.md
  • install.md
  • get-started.md
  • metrics.md
  • release-notes.md
  • Other top-level documentation files

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.8

Key enhancements in InfluxDB 3.8 and the InfluxDB 3 Explorer 1.6.

See the Blog Post

InfluxDB 3.8 is now available for both Core and Enterprise, alongside the 1.6 release of the InfluxDB 3 Explorer UI. This release is focused on operational maturity and making InfluxDB easier to deploy, manage, and run reliably in production.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 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