dom

telegraf

History

Cameron Sparr db7a4b24b6 Implement telegraf's own full metric type main reasons behind this: - make adding/removing tags cheap - make adding/removing fields cheap - make parsing cheaper - make parse -> decorate -> write out bytes metric flow much faster Refactor serializer to use byte buffer		2016-12-01 18:17:02 +00:00
..
README.md	Documentation for load balancing on graphite output servers (#1469 )	2016-07-14 09:06:00 -06:00
graphite.go	Implement telegraf's own full metric type	2016-12-01 18:17:02 +00:00
graphite_test.go	Implement telegraf's own full metric type	2016-12-01 18:17:02 +00:00

README.md

Graphite Output Plugin

This plugin writes to Graphite via raw TCP.

Configuration:

# Configuration for Graphite server to send metrics to
[[outputs.graphite]]
  ## TCP endpoint for your graphite instance.
  ## If multiple endpoints are configured, the output will be load balanced.
  ## Only one of the endpoints will be written to with each iteration.
  servers = ["localhost:2003"]
  ## Prefix metrics name
  prefix = ""
  ## Graphite output template
  ## see https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
  template = "host.tags.measurement.field"
  ## timeout in seconds for the write connection to graphite
  timeout = 2

Parameters:

Servers  []string
Prefix   string
Timeout  int
Template string

servers: List of strings, ["mygraphiteserver:2003"].
prefix: String use to prefix all sent metrics.
timeout: Connection timeout in seconds.
template: Template for graphite output format, see https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md for more details.