Closed chris-rudmin closed 8 years ago
:+1:
:+1: Yeah, this would be great to have!
@indexzero anything stopping merging this PR in?
:+1:
Hey all, I was tripped up by the README on this. The host
option does not allow a hostname to be sent with the logs. It is actually the destination for the logs to be sent to.
Setting it to os.hostname()
as I did will silently break communication with Loggly, which is bad.
The default is logs-01.loggly.com
, and I'm not aware of a use case to change that.
https://github.com/nodejitsu/node-loggly/blob/master/lib/loggly/client.js#L52
I would suggest reverting this, as it is breaks the transport silently. At a minimum, I can submit a PR to correct the README.
@bradfol thanks for finding this. An update to tests with a subsequent PR would be very helpful.
@bradfol @indexzero I misunderstood the purpose of host. Thanks for caching this. I would suggest undoing my PR, as there is not really a good reason to configure this. Apologies for troubles caused.
@indexzero @chris-rudmin Thanks guys. I've opened PR #35 to revert this.
:+1: a bit surprised native support for including a host/ip isn't already available for this integration, absolutely needed in a load-balanced/distributed environment, esp. if underlying 'loggly' node.js library supports this argument already