docs-v2/content/telegraf/v1/data_formats/input/graphite.md

title	list_title	description	menu
Graphite input data format	Graphite	Use the `graphite` input data format to parse Graphite dot buckets into Telegraf metrics.	telegraf_v1_ref name weight parent Graphite 10 Input data formats

Use the graphite input data format to parse graphite dot buckets directly into Telegraf metrics with a measurement name, a single field, and optional tags. By default, the separator is left as ., but this can be changed using the separator argument. For more advanced options, Telegraf supports specifying templates to translate graphite buckets into Telegraf metrics.

Configuration

[[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 = "graphite"

  ## This string will be used to join the matched values.
  separator = "_"

  ## Each template line requires a template pattern. It can have an optional
  ## filter before the template and separated by spaces. It can also have optional extra
  ## tags following the template. Multiple tags should be separated by commas and no spaces
  ## similar to the line protocol format. There can be only one default template.
  ## Templates support below format:
  ## 1. filter + template
  ## 2. filter + template + extra tag(s)
  ## 3. filter + template with field key
  ## 4. default template
  templates = [
    "*.app env.service.resource.measurement",
    "stats.* .host.measurement* region=eu-east,agent=sensu",
    "stats2.* .host.measurement.field",
    "measurement*"
  ]

Templates

Template patterns specify how a dot-delimited string should be mapped to and from metrics.