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	feat(nsq_consumer): Add input plugin	2016-06-23 14:06:36 +01:00
nsq_consumer.go	break telegraf registry into separate package	2017-02-06 11:16:29 +00:00
nsq_consumer_test.go	Fix unit tests for new metric implementation	2016-12-01 18:17:02 +00:00

README.md

NSQ Consumer Input Plugin

The NSQ consumer plugin polls a specified NSQD topic and adds messages to InfluxDB. This plugin allows a message to be in any of the supported data_format types.

Configuration

# Read metrics from NSQD topic(s)
[[inputs.nsq_consumer]]
  ## An array of NSQD HTTP API endpoints
  server = "localhost:4150"
  topic = "telegraf"
  channel = "consumer"
  max_in_flight = 100

  ## 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"

Testing

The nsq_consumer_test mocks out the interaction with NSQD. It requires no outside dependencies.