		# bunyan Changelog

		## bunyan 0.6.6

		- Add support to the `bunyan` CLI taking log file path args, `bunyan foo.log`,
		in addition to the usual `cat foo.log \| bunyan`.
		- Improve reliability of the default output formatting of the `bunyan` CLI.
		Before it could blow up processing log records missing some expected
		fields.


		## bunyan 0.6.5
		@@ -4,0 +13,0 @@

lib/bunyan.js

		@@ -7,3 +7,3 @@ /*

		var VERSION = "0.6.5";
		var VERSION = "0.6.6";

		@@ -10,0 +10,0 @@ // Bunyan log format version. This becomes the 'v' field on all log records.

package.json

		{
		"name": "bunyan",
		"version": "0.6.5",
		"version": "0.6.6",
		"description": "a JSON Logger library for node.js servers",
		@@ -5,0 +5,0 @@ "main": "./lib/bunyan.js",

README.md

		@@ -121,3 +121,3 @@ Bunyan -- a JSON Logger for node.js servers.

		* * *
		### A little log.child hack.

		@@ -133,8 +133,8 @@ An example and a hack: The [node-restify](https://github.com/mcavage/node-restify)

		What is that `true`? It is a small bunyan hack by which you can assert that
		you're just adding simple fields to the child logger. This makes `log.child`
		10x faster and, hence, never a worry for slowing down HTTP request handling.
		See the changelog for node-bunyan 0.3.0 for details.
		The hack is that `, true`. It is a small bunyan performance hack by which you
		can assert that you're just adding simple fields to the child logger -- i.e.
		not special fields like "level", "serializers", "streams". This makes
		`log.child` 10x faster and, hence, never a worry for slowing down HTTP
		request handling. See the changelog for node-bunyan 0.3.0 for details.

		* * *

		@@ -186,4 +186,4 @@ ## serializers

		The call source file, line and function (if not at the global level) can
		be added to log records by using the `src: true` config option:
		The source file, line and function of the log call site can be added to
		log records by using the `src: true` config option:

		@@ -215,2 +215,4 @@ var log = new Logger({src: true, ...});

		The log levels in bunyan are:

		- "fatal" (60): the service/app is going to stop or become unusable now
		@@ -223,9 +225,9 @@ - "error" (50): fatal for a particular request, but the service/app continues servicing other requests

		"debug" should be used sparingly. Information that will be useful to debug
		errors post mortem should usually be included in "info" messages if it's
		generally relevant or else with the corresponding "error" event. Don't rely on
		spewing mostly irrelevant debug messages all the time and sifting through them
		when an error occurs.
		General level usage suggestions: "debug" should be used sparingly.
		Information that will be useful to debug errors post mortem should usually
		be included in "info" messages if it's generally relevant or else with the
		corresponding "error" event. Don't rely on spewing mostly irrelevant debug
		messages all the time and sifting through them when an error occurs.

		Integers are used for the actual level values (1 for "trace", ..., 6 for
		Integers are used for the actual level values (10 for "trace", ..., 60 for
		"fatal") and constants are defined for the (Logger.TRACE ... Logger.DEBUG).
		@@ -232,0 +234,0 @@ The lowercase level names are aliases supported in the API.

bin/bunyan

Sorry, the diff of this file is not supported yet

bunyan - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics

Worsened metrics