Telegraf configurations

API token hashing is enabled by default in InfluxDB OSS 2.9.0

Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — capture any plaintext tokens you still need before you upgrade.

For more information, see Token hashing.

InfluxDB lets you automatically generate Telegraf configurations or upload custom Telegraf configurations that collect metrics and write them to InfluxDB. Telegraf retrieves configurations from InfluxDB on startup.

Use InfluxDB Telegraf configurations

With a Telegraf configuration stored in InfluxDB, the telegraf agent can retrieve the configuration from an InfluxDB HTTP(S) endpoint.

  • Ensure Telegraf has network access to InfluxDB (OSS or Cloud).

  • Start the telegraf agent using the --config flag to provide the URL of the InfluxDB Telegraf configuration. For example:

    telegraf --config http://localhost:8086/api/v2/telegrafs/<telegraf-config-id>

Setup instructions for each Telegraf configuration are provided in the InfluxDB UI.

Manage Telegraf configurations

Clone a Telegraf configuration

Use the InfluxDB UI to clone an Telegraf configuration.

Create a Telegraf configuration

Use the InfluxDB UI or the influx CLI to create an Telegraf configuration.

View Telegraf configurations

Use the InfluxDB user interface (UI) or the influx CLI to view and download InfluxDB Telegraf configurations.

Update a Telegraf configuration

Use the InfluxDB user interface (UI) or the influx CLI to update InfluxDB Telegraf configurations.

Remove a Telegraf configuration

Use the InfluxDB UI or the influx CLI to remove Telegraf configurations from InfluxDB.

Was this page helpful?

Thank you for your feedback!