Documentation

Telegraf input data formats

Telegraf input plugins consume data in one or more data formats and parse the data into Telegraf [metrics][/telegraf/v1/metrics/]. Many input plugins use configurable parsers for parsing data formats into metrics. This allows input plugins such as kafka_consumer input plugin to consume and process different data formats, such as InfluxDB line protocol or JSON. Telegraf supports the following input data formats:

Any input plugin containing the data_format option can use it to select the desired parser:

[[inputs.exec]]
  ## Commands array
  commands = ["/tmp/test.sh", "/usr/bin/mycollector --foo=bar"]

  ## measurement name suffix (for separating different commands)
  name_suffix = "_mycollector"

  ## Data format to consume.
  ## Each data format has its own unique set of configuration options, read
  ## more about them here:
  ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
  data_format = "json_v2"

Input parser plugins

When you specify a data_format in an input plugin configuration that supports it, the input plugin uses the associated parser plugin to convert data from its source format into Telegraf metrics. Many parser plugins provide additional configuration options for specifying details about your data schema and how it should map to fields in Telegraf metrics.


Was this page helpful?

Thank you for your feedback!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: