Documentation

CSV output data format

Use the csv output data format (serializer) to convert Telegraf metrics into CSV (Comma-Separated Values) lines.

Configuration

[[outputs.file]]
  files = ["stdout", "/tmp/metrics.out"]

  ## Data format to output.
  data_format = "csv"

  ## Timestamp format.
  ## Default is Unix epoch time. Use Go time layout for custom formats.
  ## See: https://golang.org/pkg/time/#Time.Format
  # csv_timestamp_format = "unix"

  ## Field separator character.
  # csv_separator = ","

  ## Output the CSV header in the first line.
  ## Enable when writing to a new file.
  ## Disable when appending or using stateless outputs to prevent
  ## headers appearing between data lines.
  # csv_header = false

  ## Prefix tag and field columns with "tag_" and "field_" respectively.
  # csv_column_prefix = false

  ## Specify column order.
  ## Use "tag." prefix for tags, "field." prefix for fields,
  ## "name" for measurement name, and "timestamp" for the timestamp.
  ## Only specified columns are included; others are dropped.
  ## Default order: timestamp, name, tags (alphabetical), fields (alphabetical)
  # csv_columns = ["timestamp", "name", "tag.host", "field.value"]

Configuration options

OptionTypeDefaultDescription
csv_timestamp_formatstring"unix"Timestamp format (Unix epoch or Go time layout)
csv_separatorstring","Field separator character
csv_headerbooleanfalseOutput CSV header row
csv_column_prefixbooleanfalsePrefix columns with tag_ or field_
csv_columnsarray[]Explicit column order (empty = all columns)

Examples

Basic CSV output

[[outputs.file]]
  files = ["/tmp/metrics.csv"]
  data_format = "csv"
  csv_header = true

Input metric:

cpu,host=server01 usage_idle=98.5,usage_user=1.2 1640000000000000000

Output:

timestamp,name,host,usage_idle,usage_user
1640000000,cpu,server01,98.5,1.2

Custom column order

[[outputs.file]]
  files = ["/tmp/metrics.csv"]
  data_format = "csv"
  csv_header = true
  csv_columns = ["timestamp", "tag.host", "field.usage_idle"]

Output:

timestamp,host,usage_idle
1640000000,server01,98.5

Custom timestamp format

[[outputs.file]]
  files = ["/tmp/metrics.csv"]
  data_format = "csv"
  csv_timestamp_format = "2006-01-02T15:04:05Z07:00"

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

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 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