continuationlabs / good-loggly Goto Github PK

Atm logging errors (which is the main thing I want to do) is almost a no go.
Since the useful error values in js are not own properties (like message and stack) they do not get serialized.
2 options:

• provide own getMessage function which would kinda solve this.
• enhance the serialize process to allow errors to be logged (like https://github.com/logentries/le_node/blob/master/src/node_modules/serialize.js#L31)

Hi,
it would be awesome if you could update this module to support good 6.0.

Thanks
Martin

Would you take a PR for adding bulk messaging support?

I recommend adding two options threshold and maxDelay like I used in good-tcp which follows the pattern established by the official good plugins, such as good-udp. These would inform the plugin if/how to buffer the messages before sending.

• threshold indicates how many messages to buffer before sending
• maxDelay tells the plugin the longest time it should hold a buffer before sending on next message (useful for programs with lower log frequency).

To maintain backward compatibility with existing plugin installations and make bulk transmission an opt-in feature, threshold would be set to 0.

Would you take a PR on how to setup Loggly for good 6 & 7? The current example only works for the older versions.

Update dependencies including good 7.x.x

I have both good-console and good-loggly registered as reporters for:

events: { log: '*', request: '*'},

I'm seeing the good-console logs appear like:

151012/172025.029, [response], http://0.0.0.0:8000: get /empire {} 200 (9ms) 

But nothing is showing up in loggly.

From within module.exports = internals.GoodLoggly = function (events, config) {, I can add this line:

this._client.log({msg: 'hello worldfoobar'}, ['david-localhost'])

and that event will appear in loggly, including the tag. So it's not a credential problem or issue with the loggly package.

I can add a console log to internals.GoodLoggly.prototype.init which appears no problem.

But if I add a console log to internals.GoodLoggly.prototype._report, it never gets printed, even as I hit routes that appear in good-console. This suggests there's a problem with one of these lines: https://github.com/fhemberger/good-loggly/blob/master/lib/index.js#L45-L46

Should I investigate squeeze? It seems to be working for good-console.

Hi,

Could you tell me how to use it with glue configuration ? I didn't managed to make it work.

Thanks.

Do this - outmoded/hapi-contrib#31

'"ops" events are not supported by Loggly'

Can you offer more information about this?