All Versions
110
Latest Version
Avg Release Cycle
22 days
Latest Release
-

Changelog History
Page 9

  • v0.13.2 Changes

    • 🌲 [issue #35] Ensure that an accidental log.info(BUFFER), where BUFFER is a node.js Buffer object, doesn't blow up.

  • v0.13.1 Changes

    • [issue #34] Ensure req.body, res.body and other request/response fields are emitted by the bunyan CLI (mostly by Rob Gulewich).

  • v0.13.0 Changes

    • 🌲 [issue #31] Re-instate defines for the (uppercase) log level names (TRACE, DEBUG, etc.) in bunyan -c "..." filtering condition code. E.g.:

      $ ... | bunyan -c 'level >= ERROR'

  • v0.12.0 Changes

    • [pull #32] bunyan -o short for more concise output (by Dave Pacheco). E.g.:

      22:56:52.856Z  INFO myservice: My message

    instead of:

        [2012-02-08T22:56:52.856Z]  INFO: myservice/123 on example.com: My message

  • v0.11.3 Changes

    • ➕ Add '--strict' option to bunyan CLI to suppress all but legal Bunyan JSON log lines. By default non-JSON, and non-Bunyan lines are passed through.

  • v0.11.2 Changes

    • [issue #30] Robust handling of 'req' field without a 'headers' subfield in bunyan CLI.
    • [issue #31] Pull the TRACE, DEBUG, et al defines from bunyan -c "..." filtering code. This was added in v0.11.1, but has a significant adverse affect.

  • v0.11.1 Changes

    • 🚀 Bad release. The TRACE et al names are bleeding into the log records when using '-c'.

    • ➕ Add defines for the (uppercase) log level names (TRACE, DEBUG, etc.) in bunyan -c "..." filtering condition code. E.g.:

      $ ... | bunyan -c 'level >= ERROR'

  • v0.11.0 Changes

    • [pull #29] Add -l/--level for level filtering, and -c/--condition for arbitrary conditional filtering (by github.com/isaacs):

      $ ... | bunyan -l error   # filter out log records below error
$ ... | bunyan -l 50      # numeric value works too
$ ... | bunyan -c 'level===50'              # equiv with -c filtering
$ ... | bunyan -c 'pid===123'               # filter on any field
$ ... | bunyan -c 'pid===123' -c '_audit'   # multiple filters

  • v0.10.0 Changes

    • 🌲 [pull #24] Support for gzip'ed log files in the bunyan CLI (by github.com/mhart):

      $ bunyan foo.log.gz
...

  • v0.9.0 Changes

    • [pull #16] Bullet proof the bunyan.stdSerializers (by github.com/rlidwka).

    • 🔀 [pull #15] The bunyan CLI will now chronologically merge multiple log streams when it is given multiple file arguments. (by github.com/davepacheco)

      $ bunyan foo.log bar.log
... merged log records ...

    • [pull #15] A new bunyan.RingBuffer stream class that is useful for keeping the last N log messages in memory. This can be a fast way to keep recent, and thus hopefully relevant, log messages. (by @dapsays, github.com/davepacheco)

    Potential uses: Live debugging if a running process could inspect those messages. One could dump recent log messages at a finer log level than is typically logged on uncaughtException.

        var ringbuffer = new bunyan.RingBuffer({ limit: 100 });
    var log = new bunyan({
        name: 'foo',
        streams: [{
            type: 'raw',
            stream: ringbuffer,
            level: 'debug'
        }]
    });

    log.info('hello world');
    console.log(ringbuffer.records);

    • ➕ Add support for "raw" streams. This is a logging stream that is given raw log record objects instead of a JSON-stringified string.

      function Collector() {
    this.records = [];
}
Collector.prototype.write = function (rec) {
    this.records.push(rec);
}
var log = new Logger({
    name: 'mylog',
    streams: [{
        type: 'raw',
        stream: new Collector()
    }]
});

    See "examples/raw-stream.js". I expect raw streams to be useful for piping Bunyan logging to separate services (e.g. http://www.loggly.com/, https://github.com/etsy/statsd) or to separate in-process handling.

    • ➕ Add test/corpus/*.log files (accidentally excluded) so the test suite actually works(!).