awatson1978 / meteor-loggly-demos

A collection of meteor demos testing different logging infrastructures.

meteor-loggly-demos

The following represents a survey of the state of logging packages in the Meteor ecosystem (June, 2017)

miktam-loggly

# atmosphere packages
miktam:loggly  

pros
Simplest library to use to get Loggly support on both client/server. Configuration is done via Meteor.settings file. Isomorphic API. Echos logs to server/browser console.

cons
Requires Meteor/Atmosphere package infrastructure.

meteor-winston

# atmosphere packages
clinical:winston-browser-logging
infinitedg:winston-loggly
infinitedg:winston

pros
The oldest Winston/Loggly integration, with support for isomorphic APIs, browser side logging, and a complete Winston infrastructure.

cons
Nonstandard capitalization and naming conventions. Requires multiple packages. Has overhead of Winston transport infrastructure. Requires Meteor/Atmosphere package infrastructure & bundling. Wrapped NPM packages cause delays in upgrades. Uses globals.

winston-loggly-bulk-demo

# npm packages
"winston": "^2.3.1"
"winston-loggly-bulk": "^1.4.2"

# atmosphere packages
clinical:winston-browser-logging

pros
Loggly recommended implementation for Node.js apps. Echos to server console. Bulk logging. Isomorphic API.

cons
Doesn't support browser side logging.

loggly-demo

# npm packages
"loggly": "^1.1.1"

pros
Cleanest NPM integration with the best ES2015 support.

cons
No support for logging from the client. Logging doesn't echo to the server console. Doesn't use globals. Very secure. The default loggly npm package is very quiet; and basically acts as a background process to securely get server events from your app to the Loggly servers.