NSQ output

[sparrc]

We should write an NSQ output sink, looks fairly straightforward since it's a Go project and they have an officially supported Go client.

Official Go client:
https://github.com/nsqio/go-nsq

Example writer:
https://github.com/nsqio/nsq/blob/master/apps/to_nsq/to_nsq.go

[samahee]

+1

[jrxFive]

Should the output sink have the option to do a lookup for the "topic" against nsqlookupd or just directly to a set of nsqd instances?

Additionally should there be changes to the default config of the Producer connection, measurements of time are in nanoseconds.

{
  "DialTimeout": 1000000000,
  "ReadTimeout": 60000000000,
  "WriteTimeout": 1000000000,
  "LocalAddr": null,
  "LookupdPollInterval": 60000000000,
  "LookupdPollJitter": 0.3,
  "MaxRequeueDelay": 900000000000,
  "DefaultRequeueDelay": 90000000000,
  "BackoffStrategy": {},
  "MaxBackoffDuration": 120000000000,
  "BackoffMultiplier": 1000000000,
  "MaxAttempts": 5,
  "LowRdyIdleTimeout": 10000000000,
  "RDYRedistributeInterval": 5000000000,
  "ClientID": "<CLIENTID>",
  "Hostname": "<HOSTNAME>",
  "UserAgent": "go-nsq/1.0.5",
  "HeartbeatInterval": 30000000000,
  "SampleRate": 0,
  "TlsV1": false,
  "TlsConfig": null,
  "Deflate": false,
  "DeflateLevel": 6,
  "Snappy": false,
  "OutputBufferSize": 16384,
  "OutputBufferTimeout": 250000000,
  "MaxInFlight": 1,
  "MsgTimeout": 0,
  "AuthSecret": ""
}

[sparrc]

@jrxFive Doing discovery would be a good idea. What exactly do you mean about the measurement times? Convering them to a different unit?

Personally I would prefer to just use what they give us to avoid confusion. It's easy enough in influx to divide by whatever scale you need.

[jrxFive]

@sparrc, I was asking if there should be an adjustments to the default config given. The time duration for those defaults are in nanoseconds was just trying to give the base unit :). But yea I agree ill stick to the defaults and incorporate a lookupd option.

[sparrc]

closed by #325