dom

telegraf

History

Cameron Sparr 2eee1b84fb break telegraf registry into separate package this is for supporting external plugins. external plugins will depend on a few telegraf interface types, as well as a common telegraf registry. this will allow external and internal plugins to both share this package and make it easier to vendor/version the whole thing semantically, which will make it easier to keep plugins supported across build and telegraf versions. see #1717		2017-02-06 11:16:29 +00:00
..
README.md	Update all readme instances of data formats	2016-04-05 14:42:20 -06:00
nats_consumer.go	break telegraf registry into separate package	2017-02-06 11:16:29 +00:00
nats_consumer_test.go	Fix unit tests for new metric implementation	2016-12-01 18:17:02 +00:00

README.md

NATS Consumer Input Plugin

The NATS consumer plugin reads from specified NATS subjects and adds messages to InfluxDB. The plugin expects messages in the Telegraf Input Data Formats. A Queue Group is used when subscribing to subjects so multiple instances of telegraf can read from a NATS cluster in parallel.

Configuration

# Read metrics from NATS subject(s)
[[inputs.nats_consumer]]
  ## urls of NATS servers
  servers = ["nats://localhost:4222"]
  ## Use Transport Layer Security
  secure = false
  ## subject(s) to consume
  subjects = ["telegraf"]
  ## name a queue group
  queue_group = "telegraf_consumers"
  ## Maximum number of metrics to buffer between collection intervals
  metric_buffer = 100000

  ## Data format to consume. 

  ## Each data format has it's 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 = "influx"