Documentation

Wavefront output data format

Use the wavefront output data format (serializer) to convert Telegraf metrics into the Wavefront Data Format.

Configuration

[[outputs.file]]
  files = ["stdout"]

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

  ## Use strict rules to sanitize metric and tag names.
  ## When enabled, forward slash (/) and comma (,) are accepted.
  # wavefront_use_strict = false

  ## Point tags to use as the source name for Wavefront.
  ## If none found, "host" is used.
  # wavefront_source_override = ["hostname", "address", "agent_host", "node_host"]

  ## Disable prefix path conversion.
  ## Default behavior (enabled): prod.prefix.name.metric.name
  ## Disabled behavior: prod.prefix_name.metric_name
  # wavefront_disable_prefix_conversion = false

Configuration options

OptionTypeDefaultDescription
wavefront_use_strictbooleanfalseUse strict sanitization rules
wavefront_source_overridearray[]Tags to use as source name
wavefront_disable_prefix_conversionbooleanfalseDisable path-style prefix conversion

Metrics

A Wavefront metric equals a single field value of a Telegraf measurement. The metric name format is: <measurement_name>.<field_name>

Only boolean and numeric fields are serialized. Other types generate an error.

Example

Input metric:

cpu,cpu=cpu0,host=testHost user=12,idle=88,system=0 1234567890

Output (Wavefront format):

"cpu.user" 12.000000 1234567890 source="testHost" "cpu"="cpu0"
"cpu.idle" 88.000000 1234567890 source="testHost" "cpu"="cpu0"
"cpu.system" 0.000000 1234567890 source="testHost" "cpu"="cpu0"

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