lookback/meteor-logger

A logger package for Meteor that logs to Loggly (or local).

Lookback Logger

A Meteor logger that logs to Loggly or local console.log on the server (no client side support as of now).

Install

Lookback Logger is available on Atmosphere as lookback:logger:

meteor add lookback:logger

Usage

A global Logger object is automatically exported from within the package and available in your app (server side only). It has the log level methods debug, warn, error and info.

Logger.info('Some logging');
Logger.warn('Watch out!');
Logger.error('Someone screwed up ...');
Logger.debug('Herp-a-derp!');

Locally, the info, warn, debug, and error methods correspond to their corresponding methods on the console object (with the exception of debug: it uses console.log).

Each Logger method takes a message as a string, and optionally an array of tags:

Logger.info('Some logging', ['my-tag']);

This can be shown in the Loggly interface.

Additionally, a global logger factory function is exported. It is used to create a logger:

someLogger = logger(params);

logger takes an object of parameters:

myLogger = logger({
  // Local logging. Defaults to true.
  local: true,

  // Loggly options. Defaults to {}. If set, local logging will be disabled.
  loggly: {
    // Options to send to the Loggly npm module.
    logglyModuleOptions: {
      token: '<your loggly token>',
      subdomain: 'foobar',
      json: true
    },
    // Params to send to Loggly with every request.
    baseParams: {
      environment: 'development',   // Defaults to process.env.NODE_ENV
      serverName: 'My Computer'
    }
  }
});

Please refer to the documentation for the loggly npm module for documentation on the logglyModuleOptions.

Tests

meteor test-packages lookback:logger

Locally:

meteor test-packages ./

Version history

• 1.1.1 - Important fix for all loggers not being called.
• 1.1.0 - Locally, output tags in front of message for easy scanning.
• 1.0.0 - Initial publish.

Contributions

Contributions are welcome. Please open issues and/or file Pull Requests.

Made by Lookback.

meteor-logger's Issues

global object Logger is not defined on server

Hi, I installed your package on Meteor 1.0.3 and tried to use it on the server.

The first file to use it is server/lib/settings.coffee but my app is crashing as Logger is not defined.

Is this reproducable for anyone else or maybe I've just done something wrong.

ReferenceError: logger is not defined

Hi there,

I installed lookback:logger this morning and put the following code in /client/etoeventSubmit.js:

Template.etoeventSubmit.events({
  'submit form': function (e) {
    e.preventDefault();

    var etoeventStart = roundToNearestQuarterHour(
      moment($(e.target).find('[name=etoeventStart]').val(), 'MM/DD/YYYY hh:mm a'));
    var etoeventStop = roundToNearestQuarterHour(
      moment($(e.target).find('[name=etoeventStop]').val(), 'MM/DD/YYYY hh:mm a'));

    myLogger.info('etoeventStart: ' + etoeventStart);
    myLogger.info('etoeventStop: ' + etoeventStop);

    // ...

});

I also made /lib/environment.js and it has the following:

myLogger = logger({
  // Local logging. Defaults to true.
  local:  true,

  // Loggly options. Defaults to {}. If set, local logging will be disabled.
  loggly: {
    // Options to send to the Loggly npm module.
    logglyModuleOptions: {
      token:     '<token>',
      subdomain: '<subdomain>',
      json:      true
      },
      // Params to send to Loggly with every request.
      baseParams: {
        environment: 'development',   // Defaults to process.env.NODE_ENV
        serverName: '<workstation name>'
    }
  }
});

What am I doing wrong? I'm fairly new to Javascript, Loggly, and Meteor so please excuse any glaring oversight I've made.