Documentation

Use Telegraf to write CSV data

Use the Telegraf file input plugin to read and parse CSV data into line protocol and write it to InfluxDB 3 Core. Telegraf is a plugin-based agent that collects metrics from different sources and writes them to specified destinations.

Configure Telegraf to read CSV files

  1. Add and enable the inputs.file plugin in your Telegraf configuration file.
  2. Use the files option to specify the list of CSV files to read. CSV files must be accessible by the Telegraf agent.
  3. Set the data_format option to csv.
  4. Define all other csv_ configuration options specific to the CSV data you want to write to InfluxDB 3 Core. For detailed information about each of the CSV format configuration options, see CSV input data format.
[[inputs.file]]
  files = ["/path/to/example.csv"]
  data_format = "csv"
  csv_header_row_count = 0
  csv_column_names = []
  csv_column_types = []
  csv_skip_rows = 0
  csv_metadata_rows = 0
  csv_metadata_separators = [":", "="]
  csv_metadata_trim_set = ""
  csv_skip_columns = 0
  csv_delimiter = ","
  csv_comment = ""
  csv_trim_space = false
  csv_tag_columns = []
  csv_measurement_column = ""
  csv_timestamp_column = ""
  csv_timestamp_format = ""
  csv_timezone = ""
  csv_skip_values = []
  csv_skip_errors = false
  csv_reset_mode = "none"

Configure Telegraf to write to InfluxDB

To send data to InfluxDB 3 Core, enable and configure the influxdb_v2 output plugin in your telegraf.conf.

[[inputs.file]]
  files = ["/path/to/example.csv"]
  data_format = "csv"
  csv_header_row_count = 0
  csv_column_names = []
  csv_column_types = []
  csv_skip_rows = 0
  csv_metadata_rows = 0
  csv_metadata_separators = [":", "="]
  csv_metadata_trim_set = ""
  csv_skip_columns = 0
  csv_delimiter = ","
  csv_comment = ""
  csv_trim_space = false
  csv_tag_columns = []
  csv_measurement_column = ""
  csv_timestamp_column = ""
  csv_timestamp_format = ""
  csv_timezone = ""
  csv_skip_values = []
  csv_skip_errors = false
  csv_reset_mode = "none"

[[outputs.influxdb_v2]]
  urls = ["http://localhost:8181"]
  token = "
AUTH_TOKEN
"
organization = "" bucket = "
DATABASE_NAME
"
content_encoding = "gzip"

Replace the following:

  • DATABASE_NAME: the name of the database to write data to

  • AUTH_TOKEN: your InfluxDB 3 Core token. Store this in a secret store or environment variable to avoid exposing the raw token string.

    Store your authorization token as an environment variable

    Avoid storing a plain text token in your Telegraf configuration file. Store the token as an environment variable and then reference the environment variable in your configuration file using string interpolation. For example:

    [[outputs.influxdb_v2]]
      urls = ["http://localhost:8181"]
      token = "${INFLUX_TOKEN}"
      # ...

Restart the Telegraf agent to apply the configuration change and write the CSV data to InfluxDB 3 Core.

Other Telegraf configuration options

The preceding examples describe Telegraf configurations necessary for writing to InfluxDB 3 Core. The influxdb_v2 output plugin provides several other configuration options. For more information, see the influxdb_v2 plugin options on GitHub.


Was this page helpful?

Thank you for your feedback!


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