TheThing
/
node-bunyan-lite
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity
node-bunyan-lite/examples/err.js

57 lines
1.6 KiB
JavaScript
Raw Normal View History

res (HTTP server response) serializer; some cleanup; 'err.js' example; Also add req/res/err details to `bunyan` tool default output mode.
2012-02-02 05:33:18 +00:00
// Example logging an error:
var http = require('http');
var Logger = require('../lib/bunyan');
- `log.clone` -> `log.child` to better reflect the relationship: streams and serializers are inherited. Streams can't be removed as part of the child creation. The child doesn't own the parent's streams (so can't close them). - Clean up Logger creation. The goal here was to ensure `log.child` usage is fast. TODO: measure that. - Add `Logger.stdSerializers.err` serializer which is necessary to get good Error object logging with node 0.6 (where core Error object properties are non-enumerable).
2012-02-04 08:08:37 +00:00
var util = require('util');
res (HTTP server response) serializer; some cleanup; 'err.js' example; Also add req/res/err details to `bunyan` tool default output mode.
2012-02-02 05:33:18 +00:00
var log = new Logger({
s/service/name/ for Logger name field. "service" is unnecessarily tied to usage for a service. No need to differ from log4j Logger "name".
2012-02-06 23:13:50 +00:00
name: "myserver",
res (HTTP server response) serializer; some cleanup; 'err.js' example; Also add req/res/err details to `bunyan` tool default output mode.
2012-02-02 05:33:18 +00:00
serializers: {
- `log.clone` -> `log.child` to better reflect the relationship: streams and serializers are inherited. Streams can't be removed as part of the child creation. The child doesn't own the parent's streams (so can't close them). - Clean up Logger creation. The goal here was to ensure `log.child` usage is fast. TODO: measure that. - Add `Logger.stdSerializers.err` serializer which is necessary to get good Error object logging with node 0.6 (where core Error object properties are non-enumerable).
2012-02-04 08:08:37 +00:00
err: Logger.stdSerializers.err, // <--- use this
res (HTTP server response) serializer; some cleanup; 'err.js' example; Also add req/res/err details to `bunyan` tool default output mode.
2012-02-02 05:33:18 +00:00
}
});
try {
throw new TypeError("boom");
} catch (err) {
log.warn({err: err}, "operation went boom: %s", err) // <--- here
}
'log.info(err)' support
2012-02-06 17:10:11 +00:00
log.info(new TypeError("how about this?")) // <--- alternatively this
try {
throw "boom string";
} catch (err) {
log.error(err)
}
res (HTTP server response) serializer; some cleanup; 'err.js' example; Also add req/res/err details to `bunyan` tool default output mode.
2012-02-02 05:33:18 +00:00
/*
$ node err.js | ../bin/bunyan -j
{
s/service/name/ for Logger name field. "service" is unnecessarily tied to usage for a service. No need to differ from log4j Logger "name".
2012-02-06 23:13:50 +00:00
"name": "myserver",
res (HTTP server response) serializer; some cleanup; 'err.js' example; Also add req/res/err details to `bunyan` tool default output mode.
2012-02-02 05:33:18 +00:00
"hostname": "banana.local",
"err": {
"stack": "TypeError: boom\n at Object.<anonymous> (/Users/trentm/tm/node-bunyan/examples/err.js:15:9)\n at Module._compile (module.js:411:26)\n at Object..js (module.js:417:10)\n at Module.load (module.js:343:31)\n at Function._load (module.js:302:12)\n at Array.0 (module.js:430:10)\n at EventEmitter._tickCallback (node.js:126:26)",
- `log.clone` -> `log.child` to better reflect the relationship: streams and serializers are inherited. Streams can't be removed as part of the child creation. The child doesn't own the parent's streams (so can't close them). - Clean up Logger creation. The goal here was to ensure `log.child` usage is fast. TODO: measure that. - Add `Logger.stdSerializers.err` serializer which is necessary to get good Error object logging with node 0.6 (where core Error object properties are non-enumerable).
2012-02-04 08:08:37 +00:00
"name": "TypeError",
res (HTTP server response) serializer; some cleanup; 'err.js' example; Also add req/res/err details to `bunyan` tool default output mode.
2012-02-02 05:33:18 +00:00
"message": "boom"
},
"level": 4,
"msg": "operation went boom: TypeError: boom",
"time": "2012-02-02T04:42:53.206Z",
"v": 0
}
$ node err.js | ../bin/bunyan
[2012-02-02T05:02:39.412Z] WARN: myserver on banana.local: operation went boom: TypeError: boom
TypeError: boom
at Object.<anonymous> (/Users/trentm/tm/node-bunyan/examples/err.js:15:9)
at Module._compile (module.js:411:26)
at Object..js (module.js:417:10)
at Module.load (module.js:343:31)
at Function._load (module.js:302:12)
at Array.0 (module.js:430:10)
at EventEmitter._tickCallback (node.js:126:26)
*/