Changelog
0.13.5
client_req
handling in the default output
of the bunyan
CLI.Changelog
0.13.4
bunyan
CLI output of a req.body
that is an
object instead of a string.Changelog
0.13.3
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.
Changelog
0.13.2
log.info(BUFFER)
, where BUFFER is
a node.js Buffer object, doesn't blow up.Changelog
0.13.1
req.body
, res.body
and other request/response fields
are emitted by the bunyan
CLI (mostly by Rob Gulewich).Changelog
0.13.0
[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'
Changelog
0.12.0
[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
Changelog
0.11.3
bunyan
CLI to suppress all but legal Bunyan JSON
log lines. By default non-JSON, and non-Bunyan lines are passed through.Changelog
0.11.2
bunyan
CLI.bunyan -c "..."
filtering code. This was added in v0.11.1, but has a significant adverse
affect.Changelog
0.11.0
[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