telegraf/plugins/outputs/graphite
Will Pearson e1faf06974 Fix problem with graphite talking to closed connections (#2171)
We were having problems with telegraf talking to
carbon-relay-ng using the graphite output. When
the carbon-relay-ng server restarted the connection
the telegraf side would go into CLOSE_WAIT but telegraf
would continue to send statistics through the connection.

Reading around it seems you need to a read from the connection
and see a EOF error. We've implemented this and added a test
that replicates roughly the error we were having.

Pair: @whpearson @joshmyers
2017-01-24 12:50:29 -08:00
..
README.md Documentation for load balancing on graphite output servers (#1469) 2016-07-14 09:06:00 -06:00
graphite.go Fix problem with graphite talking to closed connections (#2171) 2017-01-24 12:50:29 -08:00
graphite_test.go Fix problem with graphite talking to closed connections (#2171) 2017-01-24 12:50:29 -08: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