Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 446 lines (294 sloc) 15.636 kB
135163e @trentm VERSIONS, cutarelease prep
authored
1 # bunyan Changelog
2
8223e43 @trentm prep for future dev
authored
3 ## bunyan 0.14.6 (not yet released)
4
5 (nothing yet)
6
7
be4909a @trentm prepare for 0.14.5 release
authored
8 ## bunyan 0.14.5
4ef6d4d @trentm prep for future dev
authored
9
e203c9f @trentm fix long-stack-trace error serialization added in 0.14.4
authored
10 - Fix a bug in the long-stack-trace error serialization added in 0.14.4. The
11 symptom:
12
13 bunyan@0.14.4: .../node_modules/bunyan/lib/bunyan.js:1002
14 var ret = ex.stack || ex.toString();
15 ^
16 TypeError: Cannot read property 'stack' of undefined
17 at getFullErrorStack (.../node_modules/bunyan/lib/bunyan.js:1002:15)
18 ...
4ef6d4d @trentm prep for future dev
authored
19
20
883c037 @trentm prepare for 0.14.4 release
authored
21 ## bunyan 0.14.4
4944285 @trentm prep for future dev
authored
22
31fda08 @trentm note the bad release
authored
23 - **Bad release. Use 0.14.5 instead.**
79fe9cd @trentm Improve error serialization to walk the chain of `.cause()` errors
authored
24 - Improve error serialization to walk the chain of `.cause()` errors
835e945 @trentm minor edit
authored
25 from the likes of `WError` or `VError` error classes from
79fe9cd @trentm Improve error serialization to walk the chain of `.cause()` errors
authored
26 [verror](https://github.com/davepacheco/node-verror) and
9e2a6bc @trentm fix a bad error in 0.14.3
authored
27 [restify v2.0](https://github.com/mcavage/node-restify). Example:
28
29 [2012-10-11T00:30:21.871Z] ERROR: imgapi/99612 on 0525989e-2086-4270-b960-41dd661ebd7d: my-message
30 ValidationFailedError: my-message; caused by TypeError: cause-error-message
31 at Server.apiPing (/opt/smartdc/imgapi/lib/app.js:45:23)
32 at next (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:550:50)
33 at Server.setupReq (/opt/smartdc/imgapi/lib/app.js:178:9)
34 at next (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:550:50)
35 at Server.parseBody (/opt/smartdc/imgapi/node_modules/restify/lib/plugins/body_parser.js:15:33)
36 at next (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:550:50)
37 at Server.parseQueryString (/opt/smartdc/imgapi/node_modules/restify/lib/plugins/query.js:40:25)
38 at next (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:550:50)
39 at Server._run (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:579:17)
40 at Server._handle.log.trace.req (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:480:38)
41 Caused by: TypeError: cause-error-message
42 at Server.apiPing (/opt/smartdc/imgapi/lib/app.js:40:25)
43 at next (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:550:50)
44 at Server.setupReq (/opt/smartdc/imgapi/lib/app.js:178:9)
45 at next (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:550:50)
46 at Server.parseBody (/opt/smartdc/imgapi/node_modules/restify/lib/plugins/body_parser.js:15:33)
47 at next (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:550:50)
48 at Server.parseQueryString (/opt/smartdc/imgapi/node_modules/restify/lib/plugins/query.js:40:25)
49 at next (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:550:50)
50 at Server._run (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:579:17)
51 at Server._handle.log.trace.req (/opt/smartdc/imgapi/node_modules/restify/lib/server.js:480:38)
240f04a @trentm prep for future dev
authored
52
53
60c6743 @trentm prepare for 0.14.2 release
authored
54 ## bunyan 0.14.2
46c6325 @trentm prep for future dev
authored
55
8a7d743 @trentm [issue #45] Fix bunyan CLI (default output mode) to not crash on a 'r…
authored
56 - [issue #45] Fix bunyan CLI (default output mode) to not crash on a 'res'
57 field that isn't a response object, but a string.
46c6325 @trentm prep for future dev
authored
58
59
3558244 @trentm prepare for 0.14.1 release
authored
60 ## bunyan 0.14.1
d96b1c7 @trentm prep for future dev
authored
61
6c61112 @trentm [issue #44] Fix the default `bunyan` CLI output of a `res.body` that …
authored
62 - [issue #44] Fix the default `bunyan` CLI output of a `res.body` that is an
63 object instead of a string. See issue#38 for the same with `req.body`.
d96b1c7 @trentm prep for future dev
authored
64
65
60bbab8 @trentm prepare for 0.14.0 release
authored
66 ## bunyan 0.14.0
25fe445 @trentm prep for future dev
authored
67
830ae26 @trentm v0.14.0 bump for safe JSON.stringify change
authored
68 - [pull #41] Safe `JSON.stringify`ing of emitted log records to avoid blowing
69 up on circular objects (by Isaac Schlueter).
25fe445 @trentm prep for future dev
authored
70
71
5f03bda @trentm prepare for 0.13.5 release
authored
72 ## bunyan 0.13.5
e473756 @trentm prep for future dev
authored
73
44c54f4 @trentm [issue #39] Fix a bug with `client_req` handling in the default outpu…
authored
74 - [issue #39] Fix a bug with `client_req` handling in the default output
75 of the `bunyan` CLI.
e473756 @trentm prep for future dev
authored
76
77
2d33cb0 @trentm prepare for 0.13.4 release
authored
78 ## bunyan 0.13.4
8d431c4 @trentm prep for future dev
authored
79
ee6714b @trentm [issue #38] Fix the default `bunyan` CLI output of a `req.body` that …
authored
80 - [issue #38] Fix the default `bunyan` CLI output of a `req.body` that is an
81 object instead of a string.
8d431c4 @trentm prep for future dev
authored
82
83
3d0697c @trentm prepare for 0.13.3 release
authored
84 ## bunyan 0.13.3
8cfdd8b @trentm prep for future dev
authored
85
db836e2 @trentm Export `bunyan.resolveLevel(NAME-OR-NUM)` to resolve a level name or …
authored
86 - Export `bunyan.resolveLevel(NAME-OR-NUM)` to resolve a level name or number
87 to its log level number value:
835e945 @trentm minor edit
authored
88
db836e2 @trentm Export `bunyan.resolveLevel(NAME-OR-NUM)` to resolve a level name or …
authored
89 > bunyan.resolveLevel('INFO')
90 30
91 > bunyan.resolveLevel('debug')
92 20
835e945 @trentm minor edit
authored
93
db836e2 @trentm Export `bunyan.resolveLevel(NAME-OR-NUM)` to resolve a level name or …
authored
94 A side-effect of this change is that the uppercase level name is now allowed
95 in the logger constructor.
8cfdd8b @trentm prep for future dev
authored
96
97
eaf5008 @trentm prepare for 0.13.2 release
authored
98 ## bunyan 0.13.2
d3dc7df @trentm prep for future dev
authored
99
121b360 @trentm [issue #35] Ensure that an accidental `log.info(BUFFER)`, where BUFFE…
authored
100 - [issue #35] Ensure that an accidental `log.info(BUFFER)`, where BUFFER is
101 a node.js Buffer object, doesn't blow up.
d3dc7df @trentm prep for future dev
authored
102
103
1bd584a @trentm prepare for 0.13.1 release
authored
104 ## bunyan 0.13.1
525fdb1 @trentm prep for future dev
authored
105
1a9e712 @trentm [issue #34] `body` et al in request/response output by `bunyan` CLI
authored
106 - [issue #34] Ensure `req.body`, `res.body` and other request/response fields
107 are emitted by the `bunyan` CLI (mostly by Rob Gulewich).
108
525fdb1 @trentm prep for future dev
authored
109
110
7127d51 @trentm prepare for 0.13.0 release
authored
111 ## bunyan 0.13.0
01c652b @trentm prep for future dev
authored
112
31d7e34 @trentm issue #31: foudn a solution to the bleeding defines using idea from d…
authored
113 - [issue #31] Re-instate defines for the (uppercase) log level names (TRACE,
114 DEBUG, etc.) in `bunyan -c "..."` filtering condition code. E.g.:
115
116 $ ... | bunyan -c 'level >= ERROR'
01c652b @trentm prep for future dev
authored
117
118
ee61228 @trentm prepare for 0.12.0 release
authored
119 ## bunyan 0.12.0
543b68b @trentm prep for future dev
authored
120
c7e9987 @trentm rev to 0.12.0 and note the '-o short' change
authored
121 - [pull #32] `bunyan -o short` for more concise output (by Dave Pacheco). E.g.:
122
123 22:56:52.856Z INFO myservice: My message
124
125 instead of:
126
127 [2012-02-08T22:56:52.856Z] INFO: myservice/123 on example.com: My message
543b68b @trentm prep for future dev
authored
128
129
64112ee @trentm prepare for 0.11.3 release
authored
130 ## bunyan 0.11.3
19bc3ce @trentm prep for future dev
authored
131
4ad39fe @trentm '--strict' option for CLI
authored
132 - Add '--strict' option to `bunyan` CLI to suppress all but legal Bunyan JSON
133 log lines. By default non-JSON, and non-Bunyan lines are passed through.
19bc3ce @trentm prep for future dev
authored
134
135
208b949 @trentm prepare for 0.11.2 release
authored
136 ## bunyan 0.11.2
02d72b0 @trentm prep for future dev
authored
137
f0a119a @trentm [issue #30] Robust handling of 'req' field without a 'headers' subfie…
authored
138 - [issue #30] Robust handling of 'req' field without a 'headers' subfield
139 in `bunyan` CLI.
cfa64e9 @trentm issue #31: DEBUG et al defines in '-c' scripts bleed into log records
authored
140 - [issue #31] Pull the TRACE, DEBUG, et al defines from `bunyan -c "..."`
141 filtering code. This was added in v0.11.1, but has a significant adverse
142 affect.
02d72b0 @trentm prep for future dev
authored
143
144
67da837 @trentm prepare for 0.11.1 release
authored
145 ## bunyan 0.11.1
6c26bf0 @trentm prep for future dev
authored
146
156d2c4 @trentm bad release
authored
147 - **Bad release. The TRACE et al names are bleeding into the log records
148 when using '-c'.**
0620b27 @trentm TRACE, DEBUG, et al in `bunayn -c "..."` filter code.
authored
149 - Add defines for the (uppercase) log level names (TRACE, DEBUG, etc.) in
150 `bunyan -c "..."` filtering condition code. E.g.:
151
152 $ ... | bunyan -c 'level >= ERROR'
6c26bf0 @trentm prep for future dev
authored
153
154
8ae15c9 @trentm prepare for 0.11.0 release
authored
155 ## bunyan 0.11.0
dd94067 @trentm prep for future dev
authored
156
f3fcc9c @trentm Bump to v0.11.0. Change log update. Some -h output tweak.
authored
157 - [pull #29] Add -l/--level for level filtering, and -c/--condition for
158 arbitrary conditional filtering (by github.com/isaacs):
159
160 $ ... | bunyan -l error # filter out log records below error
161 $ ... | bunyan -l 50 # numeric value works too
162 $ ... | bunyan -c 'level===50' # equiv with -c filtering
163 $ ... | bunyan -c 'pid===123' # filter on any field
164 $ ... | bunyan -c 'pid===123' -c '_audit' # multiple filters
dd94067 @trentm prep for future dev
authored
165
166
c872a2a @trentm prepare for 0.10.0 release
authored
167 ## bunyan 0.10.0
efab2b0 @trentm prep for future dev
authored
168
27a035f @trentm rev to 0.10.0 and add changelog for mhart's gzip addition
authored
169 - [pull #24] Support for gzip'ed log files in the bunyan CLI (by
170 github.com/mhart):
171
172 $ bunyan foo.log.gz
173 ...
efab2b0 @trentm prep for future dev
authored
174
175
8873f16 @trentm prepare for 0.9.0 release
authored
176 ## bunyan 0.9.0
c5ba5c0 @trentm support for 'raw' streams
authored
177
66afe81 @trentm [pull #16] Bullet proof the `bunyan.stdSerializers`
authored
178 - [pull #16] Bullet proof the `bunyan.stdSerializers` (by github.com/rlidwka).
179
9f8281e @trentm changelog entries for dap's additions
authored
180 - [pull #15] The `bunyan` CLI will now chronologically merge multiple log
181 streams when it is given multiple file arguments. (by github.com/davepacheco)
182
183 $ bunyan foo.log bar.log
184 ... merged log records ...
185
186 - [pull #15] A new `bunyan.RingBuffer` stream class that is useful for
187 keeping the last N log messages in memory. This can be a fast way to keep
188 recent, and thus hopefully relevant, log messages. (by @dapsays,
189 github.com/davepacheco)
190
37a1447 @trentm per issue #8 change the way a raw stream is handled
authored
191 Potential uses: Live debugging if a running process could inspect those
192 messages. One could dump recent log messages at a finer log level than is
193 typically logged on
9f8281e @trentm changelog entries for dap's additions
authored
194 [`uncaughtException`](http://nodejs.org/docs/latest/api/all.html#all_event_uncaughtexception).
195
196 var ringbuffer = new bunyan.RingBuffer({ limit: 100 });
197 var log = new bunyan({
37a1447 @trentm per issue #8 change the way a raw stream is handled
authored
198 name: 'foo',
199 streams: [{
200 type: 'raw',
201 stream: ringbuffer,
202 level: 'debug'
203 }]
9f8281e @trentm changelog entries for dap's additions
authored
204 });
205
206 log.info('hello world');
1eed1fa @trentm use RingBuffer.records instead of RingBuffer.enties (related to pull …
authored
207 console.log(ringbuffer.records);
9f8281e @trentm changelog entries for dap's additions
authored
208
c5ba5c0 @trentm support for 'raw' streams
authored
209 - Add support for "raw" streams. This is a logging stream that is given
210 raw log record objects instead of a JSON-stringified string.
211
212 function Collector() {
213 this.records = [];
214 }
215 Collector.prototype.write = function (rec) {
216 this.records.push(rec);
217 }
218 var log = new Logger({
219 name: 'mylog',
37a1447 @trentm per issue #8 change the way a raw stream is handled
authored
220 streams: [{
221 type: 'raw',
222 stream: new Collector()
223 }]
c5ba5c0 @trentm support for 'raw' streams
authored
224 });
225
9f8281e @trentm changelog entries for dap's additions
authored
226 See "examples/raw-stream.js". I expect raw streams to be useful for
37a1447 @trentm per issue #8 change the way a raw stream is handled
authored
227 piping Bunyan logging to separate services (e.g. <http://www.loggly.com/>,
9f8281e @trentm changelog entries for dap's additions
authored
228 <https://github.com/etsy/statsd>) or to separate in-process handling.
80c009a @trentm prep for future dev
authored
229
37a1447 @trentm per issue #8 change the way a raw stream is handled
authored
230 - Add test/corpus/*.log files (accidentally excluded) so the test suite
231 actually works(!).
80c009a @trentm prep for future dev
authored
232
233
9e251a5 @trentm prepare for 0.8.0 release
authored
234 ## bunyan 0.8.0
858150b @trentm pull #21: some style tweaks, add stream to error event args, test cas…
authored
235
236 - [pull #21] Bunyan loggers now re-emit `fs.createWriteStream` error events.
237 By github.com/EvanOxfeld. See "examples/handle-fs-error.js" and
238 "test/error-event.js" for details.
239
240 var log = new Logger({name: 'mylog', streams: [{path: FILENAME}]});
241 log.on('error', function (err, stream) {
242 // Handle error writing to or creating FILENAME.
243 });
13b36fb @trentm prep for future dev
authored
244
4f28afc @trentm note it
authored
245 - jsstyle'ing (via `make check`)
13b36fb @trentm prep for future dev
authored
246
247
2daf47c @trentm prepare for 0.7.0 release
authored
248 ## bunyan 0.7.0
6e0d1ec @trentm prep for future dev
authored
249
c7d5f8b @trentm [issue #12] Add `bunyan.createLogger(OPTIONS)` form, as is more typic…
authored
250 - [issue #12] Add `bunyan.createLogger(OPTIONS)` form, as is more typical in
251 node.js APIs. This'll eventually become the preferred form.
6e0d1ec @trentm prep for future dev
authored
252
253
6d9aa4f @trentm prepare for 0.6.9 release
authored
254 ## bunyan 0.6.9
fcbecef @trentm prep for future dev
authored
255
8f1c8ad @trentm color 'src' info red in default bunyan CLI coloring
authored
256 - Change `bunyan` CLI default output to color "src" info red. Before the "src"
257 information was uncolored. The "src" info is the filename, line number and
258 function name resulting from using `src: true` in `Logger` creation. I.e.,
259 the `(/Users/trentm/tm/node-bunyan/examples/hi.js:10)` in:
260
261 [2012-04-10T22:28:58.237Z] INFO: myapp/39339 on banana.local (/Users/trentm/tm/node-bunyan/examples/hi.js:10): hi
262
ea39bf0 @trentm Bunyan CLI tweak to show an 'err' field that doesn't have a 'stack'.
authored
263 - Tweak `bunyan` CLI default output to still show an "err" field if it doesn't
264 have a "stack" attribute.
265
fcbecef @trentm prep for future dev
authored
266
d4bbc70 @trentm prepare for 0.6.8 release
authored
267 ## bunyan 0.6.8
993f9d8 @trentm prep for future dev
authored
268
8ea2533 @trentm Fix bad bug with the "fast child" path: `log.child({...}, true)`.
authored
269 - Fix bad bug in `log.child({...}, true);` where the added child fields **would
270 be added to the parent's fields**. This bug only existed for the "fast child"
271 path (that second `true` argument). A side-effect of fixing this is that
272 the "fast child" path is only 5 times as fast as the regular `log.child`,
273 instead of 10 times faster.
274
993f9d8 @trentm prep for future dev
authored
275
cfa6d92 @trentm prepare for 0.6.7 release
authored
276 ## bunyan 0.6.7
a834151 @trentm prep for future dev
authored
277
9f8f6e7 @trentm changelog message for Mike's pull
authored
278 - [issue #6] Fix bleeding 'type' var to global namespace. (Thanks Mike!)
279
a834151 @trentm prep for future dev
authored
280
dd14781 @trentm prepare for 0.6.6 release
authored
281 ## bunyan 0.6.6
77b99b6 @trentm prep for future dev
authored
282
9feb9c8 @trentm CLI file args: bunyan foo.log bar.log
authored
283 - Add support to the `bunyan` CLI taking log file path args, `bunyan foo.log`,
284 in addition to the usual `cat foo.log | bunyan`.
285 - Improve reliability of the default output formatting of the `bunyan` CLI.
286 Before it could blow up processing log records missing some expected
287 fields.
288
77b99b6 @trentm prep for future dev
authored
289
d49bee3 @trentm prepare for 0.6.5 release
authored
290 ## bunyan 0.6.5
b52b1b6 @trentm prep for future dev
authored
291
92a2e9d @trentm colored bunyan CLI output, and --color option
authored
292 - ANSI coloring output from `bunyan` CLI tool (for the default output mode/style).
293 Also add the '--color' option to force coloring if the output stream is not
887f407 @trentm --no-color option
authored
294 a TTY, e.g. `cat my.log | bunyan --color | less -R`. Use `--no-color` to
295 disable coloring, e.g. if your terminal doesn't support ANSI codes.
296 - Add 'level' field to log record before custom fields for that record. This
297 just means that the raw record JSON will show the 'level' field earlier,
298 which is a bit nicer for raw reading.
0f02707 @trentm put 'level' field earlier in record
authored
299
b52b1b6 @trentm prep for future dev
authored
300
d0fb966 @trentm prepare for 0.6.4 release
authored
301 ## bunyan 0.6.4
40ec83b @trentm [issue #5] Fix `log.info() -> boolean` to work properly. Previous all…
authored
302
303 - [issue #5] Fix `log.info() -> boolean` to work properly. Previous all were
304 returning false. Ditto all trace/debug/.../fatal methods.
305
306
39920c5 @trentm prepare for 0.6.3 release
authored
307 ## bunyan 0.6.3
38ea773 @trentm prep for future dev
authored
308
519f263 @trentm Allow an optional `msg` and arguments to the `log.info(<Error> err)` …
authored
309 - Allow an optional `msg` and arguments to the `log.info(<Error> err)` logging
310 form. For example, before:
311
312 log.debug(my_error_instance) // good
313 log.debug(my_error_instance, "boom!") // wasn't allowed
314
315 Now the latter is allowed if you want to expliciting set the log msg. Of course
316 this applies to all the `log.{trace|debug|info...}()` methods.
317
61ff403 @trentm clearer output for fields with spaces or empty string in bunyan cli o…
authored
318 - `bunyan` cli output: clarify extra fields with quoting if empty or have
319 spaces. E.g. 'cmd' and 'stderr' in the following:
320
321 [2012-02-12T00:30:43.736Z] INFO: mo-docs/43194 on banana.local: buildDocs results (req_id=185edca2-2886-43dc-911c-fe41c09ec0f5, route=PutDocset, error=null, stderr="", cmd="make docs")
322
38ea773 @trentm prep for future dev
authored
323
5e12452 @trentm prepare for 0.6.2 release
authored
324 ## bunyan 0.6.2
5361795 @trentm prep for future dev
authored
325
a14cea4 @trentm changelog for npm publish guard
authored
326 - Fix/guard against unintended inclusion of some files in npm published package
327 due to <https://github.com/isaacs/npm/issues/2144>
328
5361795 @trentm prep for future dev
authored
329
aa52789 @trentm prepare for 0.6.1 release
authored
330 ## bunyan 0.6.1
9c8f4e1 @trentm prep for future dev
authored
331
8c0e3ab @trentm npmignore to avoid crud in published packages
authored
332 - Internal: starting jsstyle usage.
333 - Internal: add .npmignore. Previous packages had reams of bunyan crud in them.
334
9c8f4e1 @trentm prep for future dev
authored
335
de2b661 @trentm prepare for 0.6.0 release
authored
336 ## bunyan 0.6.0
c12a90a @trentm issue #4: add 'pid' automatic log record field
authored
337
338 - Add 'pid' automatic log record field.
e8581c5 @trentm prep for future dev
authored
339
340
7f262ba @trentm prepare for 0.5.3 release
authored
341 ## bunyan 0.5.3
63f97b8 @trentm prep for future dev
authored
342
dda4603 @trentm mention 'client_req' in changelog
authored
343 - Add 'client_req' (HTTP client request) standard formatting in `bunyan` CLI
344 default output.
d531072 @trentm bunyan CLI output includes all keys
authored
345 - Improve `bunyan` CLI default output to include *all* log record keys. Unknown keys
346 are either included in the first line parenthetical (if short) or in the indented
347 subsequent block (if long or multiline).
348
63f97b8 @trentm prep for future dev
authored
349
768b2de @trentm prepare for 0.5.2 release
authored
350 ## bunyan 0.5.2
a8b054e @trentm prep for future dev
authored
351
9f5581b @trentm issue #3: more type checking of Logger ctor options and log.child opt…
authored
352 - [issue #3] More type checking of `new Logger(...)` and `log.child(...)`
353 options.
450e4eb @trentm start a test suite
authored
354 - Start a test suite.
355
a8b054e @trentm prep for future dev
authored
356
74f3787 @trentm prepare for 0.5.1 release
authored
357 ## bunyan 0.5.1
969ac69 @trentm prep for future dev
authored
358
3649708 @trentm note issue #2 for this
authored
359 - [issue #2] Add guard on `JSON.stringify`ing of log records before emission.
360 This will prevent `log.info` et al throwing on record fields that cannot be
361 represented as JSON. An error will be printed on stderr and a clipped log
362 record emitted with a 'bunyanMsg' key including error details. E.g.:
887f407 @trentm --no-color option
authored
363
1a0cd4b @trentm issue #2: Add guard on `JSON.stringify`ing of log records before emis…
authored
364 bunyan: ERROR: could not stringify log record from /Users/trentm/tm/node-bunyan/examples/unstringifyable.js:12: TypeError: Converting circular structure to JSON
365 {
366 "name": "foo",
367 "hostname": "banana.local",
368 "bunyanMsg": "bunyan: ERROR: could not stringify log record from /Users/trentm/tm/node-bunyan/examples/unstringifyable.js:12: TypeError: Converting circular structure to JSON",
369 ...
370
887f407 @trentm --no-color option
authored
371 Some timing shows this does effect log speed:
372
1a0cd4b @trentm issue #2: Add guard on `JSON.stringify`ing of log records before emis…
authored
373 $ node tools/timeguard.js # before
374 Time try/catch-guard on JSON.stringify:
375 - log.info: 0.07365ms per iteration
376 $ node tools/timeguard.js # after
377 Time try/catch-guard on JSON.stringify:
378 - log.info: 0.07368ms per iteration
3649708 @trentm note issue #2 for this
authored
379
969ac69 @trentm prep for future dev
authored
380
cb41c7e @trentm prepare for 0.5.0 release
authored
381 ## bunyan 0.5.0
543ef15 @trentm 'log.info(err)' support
authored
382
25b8eea @trentm Use 10/20/... instead of 1/2/... for level constant values.
authored
383 - Use 10/20/... instead of 1/2/... for level constant values. Ostensibly this
384 allows for intermediary levels from the defined "trace/debug/..." set.
385 However, that is discouraged. I'd need a strong user argument to add
386 support for easily using alternative levels. Consider using a separate
387 JSON field instead.
140c9fd @trentm s/service/name/ for Logger name field. "service" is unnecessarily tie…
authored
388 - s/service/name/ for Logger name field. "service" is unnecessarily tied
389 to usage for a service. No need to differ from log4j Logger "name".
352c417 @trentm Add `log.level(...)` and `log.levels(...)` API for changing logger st…
authored
390 - Add `log.level(...)` and `log.levels(...)` API for changing logger stream
391 levels.
392 - Add `TRACE|DEBUG|INFO|WARN|ERROR|FATAL` level constants to exports.
543ef15 @trentm 'log.info(err)' support
authored
393 - Add `log.info(err)` special case for logging an `Error` instance. For
394 example `log.info(new TypeError("boom")` will produce:
395
396 ...
397 "err": {
398 "message": "boom",
399 "name": "TypeError",
400 "stack": "TypeError: boom\n at Object.<anonymous> ..."
401 },
402 "msg": "boom",
403 ...
141253c @trentm prep for future dev
authored
404
405
12f2701 @trentm prepare for 0.4.0 release
authored
406 ## bunyan 0.4.0
e934baf @trentm v0.4: add 'src' call source location info support (the Yunong release)
authored
407
408 - Add `new Logger({src: true})` config option to have a 'src' attribute be
409 automatically added to log records with the log call source info. Example:
410
411 "src": {
412 "file": "/Users/trentm/tm/node-bunyan/examples/src.js",
413 "line": 20,
414 "func": "Wuzzle.woos"
415 },
d7e499b @trentm prep for future dev
authored
416
417
7c94825 @trentm prepare for 0.3.0 release
authored
418 ## bunyan 0.3.0
6806112 @trentm - `log.clone` -> `log.child` to better reflect the relationship: stre…
authored
419
40777aa @trentm 'log.child(..., true)' support for 10x faster with 'simple' field add…
authored
420 - `log.child(options[, simple])` Added `simple` boolean arg. Set `true` to
421 assert that options only add fields (no config changes). Results in a 10x
887f407 @trentm --no-color option
authored
422 speed increase in child creation. See "tools/timechild.js". On my Mac,
40777aa @trentm 'log.child(..., true)' support for 10x faster with 'simple' field add…
authored
423 "fast child" creation takes about 0.001ms. IOW, if your app is dishing
424 10,000 req/s, then creating a log child for each request will take
425 about 1% of the request time.
6806112 @trentm - `log.clone` -> `log.child` to better reflect the relationship: stre…
authored
426 - `log.clone` -> `log.child` to better reflect the relationship: streams and
427 serializers are inherited. Streams can't be removed as part of the child
428 creation. The child doesn't own the parent's streams (so can't close them).
429 - Clean up Logger creation. The goal here was to ensure `log.child` usage
430 is fast. TODO: measure that.
431 - Add `Logger.stdSerializers.err` serializer which is necessary to get good
432 Error object logging with node 0.6 (where core Error object properties
433 are non-enumerable).
d123784 @trentm prep for future dev
authored
434
435
7798f40 @trentm prepare for 0.2.0 release
authored
436 ## bunyan 0.2.0
aecc04f @trentm prep for subsequent release
authored
437
a475a1a @trentm 0.2: specing core log record fields (mainly)
authored
438 - Spec'ing core/recommended log record fields.
439 - Add `LOG_VERSION` to exports.
440 - Improvements to request/response serializations.
aecc04f @trentm prep for subsequent release
authored
441
442
7539c03 @trentm prepare for 0.1.0 release
authored
443 ## bunyan 0.1.0
135163e @trentm VERSIONS, cutarelease prep
authored
444
445 First release.
Something went wrong with that request. Please try again.