Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Jan 10, 2015
  1. 0.6.22

    Gareth Jones authored
  2. Merge pull request #240 from vivocha/vivocha-0.6.20

    authored
    Vivocha 0.6.20
  3. Merge pull request #260 from DerKnerd/patch-1

    authored
    Update README.md
  4. Merge pull request #261 from boljen/clusterpid

    authored
    added cluster identifier support
  5. Merge pull request #264 from FleetingClouds/master

    authored
    Force bundling of appenders/console
  6. Merge pull request #266 from sc2bigjoe/patch-1

    authored
    Update smtp.js
  7. Merge pull request #268 from askhogan/master

    authored
    Allow for blank tokens due to dynamic data
  8. Merge pull request #269 from Nekle/master

    authored
    add options to reload function
Commits on Dec 27, 2014
  1. Fuxian Ding

    add options to reload function

    Nekle authored
    if `cwd` is included in option, reload will not work
Commits on Dec 24, 2014
  1. Patrick Hogan

    added null tests

    askhogan authored
Commits on Dec 21, 2014
  1. Patrick Hogan

    Allow for blank tokens due to dynamic data

    askhogan authored
    Metadata for users such as name, email, etc are not always present for users.  For example, I am running express and I want to log the %x{company}%x{username} so that when I look at my logs I can immediately understand which user this affects.  Or for example, I could log %x{payingOrTial} the type of user.  
    
    This works well when the user is logged in.  However, my logger encompasses everything.  I log when the server boots up.  I log during the login screen where a user is not yet logged in.  In these circumstances there is no way to retrieve this metadata.
    
    So for example
    
    ```
    "username": function () {
                var session = require('continuation-local-storage').getNamespace('api.callinize');
                if(!session) session = require('continuation-local-storage').getNamespace('dashboard.callinize');
                var username = session && session.get('user') && session.get('user').username;
                if(!username) return "";
                return " " + username + " ";
            }
    ```
    
    I try to get the metadata.  If I get no metdata I return a blank string.  Unfortunately, in the current implementation, due to the OR operator, even if I have a replacement of "" || matchedString, 
    
    ```
      replaceToken(conversionCharacter, loggingEvent, specifier) || 
              matchedString;
    ```
    
    the blank string equals false and puts the token in the log instead of the blank string.  This makes the log lines get long with information that is not relevant.  The better thing to do is simply allow for blank strings.  This lets the user have control over their logs and also allows for more metadata to go in the logs, without having to pick only metadata that is always present.
Commits on Dec 17, 2014
  1. sc2bigjoe

    Update smtp.js

    sc2bigjoe authored
    added the ability for smtp appender to send message as html instead of plaintext. in your log4js.config file simply include "html": "true", to write out as html, otherwise it will send plaintext
Commits on Dec 9, 2014
  1. Martin 'Hasan' Bramwell

    Force bundling of appenders/console

    martinhbramwell authored
     Changes to be committed:
    	modified:   lib/log4js.js
Commits on Dec 1, 2014
  1. boljen
  2. boljen
Commits on Nov 28, 2014
  1. Imanuel Ulbricht

    Update README.md

    DerKnerd authored
Commits on Nov 15, 2014
  1. Merge pull request #258 from osher/patch-4

    authored
    fix bug: headers are changed after log entry emits
Commits on Nov 5, 2014
  1. osher

    0.8 compatibility

    osher authored
  2. osher
Commits on Nov 4, 2014
  1. osher

    fix bug: headers are changed after log entry emits

    osher authored
    In the original version, the following operation looks synchronic, however it is not:
    
    ```
    res.end = end;
    res.end(data,enc);
    
    //emit the log entry 
    ```
    
    In fact, it starts a series of async operations, in which the request may yet be changed after the request log has already been emitted
    (in our case - a change on request headers was observed, probably by some low level hook or hacky wrap of some http.ServerResponse method that's involved on the process - but called asynchronously)
    what leads to situation that the request log does not capture valid data.
    (observed by us:
     - request headers
     - calculated end time, when concerning big content
    )
    
    The fix just used `setTimeout(function() { /*emit the log entry*/ }, 1)`, but I'm afraid it may not hold true for big contents.
    Well. maybe the headers part will, but the response time calculation will lie.
    
    The fix relays on: http://nodejs.org/api/http.html#http_event_finish
Commits on Sep 10, 2014
  1. 0.6.21

    Gareth Jones authored
  2. added license info

    Gareth Jones authored
  3. Merge pull request #242 from marcelog/marcelog_logstash_udp_appender

    authored
    adding logstash UDP appender
  4. Merge pull request #243 from laenger/master

    authored
    pass options to wrapped appender in logLevelFilter
  5. Marcelo Gornstein

    adding logstash UDP appender

    marcelog authored
Commits on Sep 9, 2014
  1. Christian Langer
Commits on Sep 8, 2014
  1. lmalheiro
  2. lmalheiro

    Removed property 'level' from the file appender, because that functio…

    lmalheiro authored
    …nality is provided by appender logLevelFilter.
  3. lmalheiro
Commits on Sep 2, 2014
  1. lmalheiro
  2. Merge pull request #239 from lazutkin/gh-238

    authored
    Closes #238 Updated async library
Commits on Sep 1, 2014
  1. lmalheiro
  2. lmalheiro
Commits on Aug 29, 2014
  1. lmalheiro

    Log compression.

    lmalheiro authored
  2. lmalheiro

    Adds subcategories to the appenders and loggers. Adds property "level…

    lmalheiro authored
    …" at the file appender to limit the levels that a file appender accepts.
    
    Creates a MARK category that always write to the log. That's useful to write things like '---- STARTED ----'.
Something went wrong with that request. Please try again.