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

Changelog History
Page 8

  • v0.15.0 Changes

    • 🌲 issue #48: Dtrace support! The elevator pitch is you can watch all logging from all Bunyan-using process with something like this:

      dtrace -x strsize=4k -qn 'bunyan*:::log-*{printf("%d: %s: %s", pid, probefunc, copyinstr(arg0))}'

    And this can include log levels below what the service is actually configured to log. E.g. if the service is only logging at INFO level and you need to see DEBUG log messages, with this you can. Obviously this only works on dtrace-y platforms: Illumos derivatives of SunOS (e.g. SmartOS, OmniOS), Mac, FreeBSD.

    Or get the bunyan CLI to render logs nicely:

        dtrace -x strsize=4k -qn 'bunyan*:::log-*{printf("%s", copyinstr(arg0))}' | bunyan

    See https://github.com/trentm/node-bunyan#dtrace-support for details. By Bryan Cantrill.

  • v0.14.6 Changes

    • Export bunyan.safeCycles(). This may be useful for custom type == "raw" streams that may do JSON stringification of log records themselves. Usage:

      var str = JSON.stringify(rec, bunyan.safeCycles());

    • 🌲 [issue #49] Allow a log.child() to specify the level of inherited streams. For example:

      # Before
var childLog = log.child({...});
childLog.level('debug');

# After
var childLog = log.child({..., level: 'debug'});

    • 👌 Improve the Bunyan CLI crash message to make it easier to provide relevant details in a bug report.

  • v0.14.5 Changes

    • 🛠 Fix a bug in the long-stack-trace error serialization added in 0.14.4. The symptom:

      [email protected]: .../node_modules/bunyan/lib/bunyan.js:1002
  var ret = ex.stack || ex.toString();
              ^
TypeError: Cannot read property 'stack' of undefined
    at getFullErrorStack (.../node_modules/bunyan/lib/bunyan.js:1002:15)
    ...

  • v0.14.4 Changes

    • 🚀 Bad release. Use 0.14.5 instead.

    • 👌 Improve error serialization to walk the chain of .cause() errors from the likes of WError or VError error classes from verror and restify v2.0. Example:

      [2012-10-11T00:30:21.871Z] ERROR: imgapi/99612 on 0525989e-2086-4270-b960-41dd661ebd7d: my-message
    ValidationFailedError: my-message; caused by TypeError: cause-error-message
        at Server.apiPing (/opt/smartdc/imgapi/lib/app.js:45:23)
        at next (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:550:50)
        at Server.setupReq (/opt/smartdc/imgapi/lib/app.js:178:9)
        at next (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:550:50)
        at Server.parseBody (/opt/smartdc/imgapi/node_modules/restify/lib/plugins/body_parser.js:15:33)
        at next (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:550:50)
        at Server.parseQueryString (/opt/smartdc/imgapi/node_modules/restify/lib/plugins/query.js:40:25)
        at next (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:550:50)
        at Server._run (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:579:17)
        at Server._handle.log.trace.req (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:480:38)
    Caused by: TypeError: cause-error-message
        at Server.apiPing (/opt/smartdc/imgapi/lib/app.js:40:25)
        at next (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:550:50)
        at Server.setupReq (/opt/smartdc/imgapi/lib/app.js:178:9)
        at next (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:550:50)
        at Server.parseBody (/opt/smartdc/imgapi/node_modules/restify/lib/plugins/body_parser.js:15:33)
        at next (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:550:50)
        at Server.parseQueryString (/opt/smartdc/imgapi/node_modules/restify/lib/plugins/query.js:40:25)
        at next (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:550:50)
        at Server._run (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:579:17)
        at Server._handle.log.trace.req (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:480:38)

  • v0.14.2 Changes

    • 0️⃣ [issue #45] Fix bunyan CLI (default output mode) to not crash on a 'res' field that isn't a response object, but a string.

  • v0.14.1 Changes

    • 0️⃣ [issue #44] Fix the default bunyan CLI output of a res.body that is an object instead of a string. See issue#38 for the same with req.body.

  • v0.14.0 Changes

    • 🌲 [pull #41] Safe JSON.stringifying of emitted log records to avoid blowing up on circular objects (by Isaac Schlueter).

  • v0.13.5 Changes

    • 0️⃣ [issue #39] Fix a bug with client_req handling in the default output of the bunyan CLI.

  • v0.13.4 Changes

    • 0️⃣ [issue #38] Fix the default bunyan CLI output of a req.body that is an object instead of a string.

  • v0.13.3 Changes

    • Export bunyan.resolveLevel(NAME-OR-NUM) to resolve a level name or number to its log level number value:

      > bunyan.resolveLevel('INFO')
30
> bunyan.resolveLevel('debug')
20

    A side-effect of this change is that the uppercase level name is now allowed in the logger constructor.