f0a119a306
[issue #30 ] Robust handling of 'req' field without a 'headers' subfield in `bunyan` CLI.
2012-08-08 22:27:49 -07:00
cfa64e9f97
issue #31 : DEBUG et al defines in '-c' scripts bleed into log records
2012-08-08 22:03:57 -07:00
156d2c4aff
bad release
2012-08-08 20:25:15 -07:00
02d72b0a9d
prep for future dev
2012-08-08 11:58:43 -07:00
67da83727d
prepare for 0.11.1 release
2012-08-08 11:58:02 -07:00
0620b2793d
TRACE, DEBUG, et al in `bunayn -c "..."` filter code.
...
E.g.:
$ ... | bunyan -c 'level >= ERROR'
2012-08-08 11:57:13 -07:00
6c26bf0038
prep for future dev
2012-08-07 22:36:42 -07:00
8ae15c994b
prepare for 0.11.0 release
2012-08-07 22:35:38 -07:00
f3fcc9c7ca
Bump to v0.11.0. Change log update. Some -h output tweak.
2012-08-07 22:13:38 -07:00
dd940678c7
prep for future dev
2012-06-21 22:49:24 -07:00
c872a2a9b6
prepare for 0.10.0 release
2012-06-21 22:49:13 -07:00
27a035fc6e
rev to 0.10.0 and add changelog for mhart's gzip addition
2012-06-21 22:49:04 -07:00
efab2b0b3f
prep for future dev
2012-06-21 20:06:10 -07:00
8873f1655d
prepare for 0.9.0 release
2012-06-21 20:05:57 -07:00
66afe81ee9
[pull #16 ] Bullet proof the `bunyan.stdSerializers`
2012-06-21 17:24:06 -07:00
1eed1fac19
use RingBuffer.records instead of RingBuffer.enties (related to pull #15 )
2012-06-21 14:53:05 -07:00
37a1447f22
per issue #8 change the way a raw stream is handled
...
"raw" is now a stream "type" isntead of a separate attribute. The
idea is that writing raw objects (instead of JSON-stringified stings)
to, e.g. a file WriteStream isn't useful. So, lets re-use the stream
"type" field instead of an additional "raw" field.
2012-06-21 14:49:04 -07:00
9f8281e651
changelog entries for dap's additions
2012-06-20 17:02:43 -07:00
c5ba5c0147
support for 'raw' streams
2012-06-20 16:04:23 -07:00
7e90e07865
Add test/corpus/*.log files (accidentally excluded) so that test suite works
2012-06-05 17:22:25 -07:00
80c009a0d7
prep for future dev
2012-06-04 23:31:10 -07:00
9e251a5470
prepare for 0.8.0 release
2012-06-04 23:30:58 -07:00
858150bbd2
pull #21 : some style tweaks, add stream to error event args, test case, example, changelog
2012-06-04 23:13:50 -07:00
4f28afc7a2
note it
2012-04-28 01:01:54 -07:00
13b36fb366
prep for future dev
2012-04-27 16:21:23 -07:00
2daf47c11c
prepare for 0.7.0 release
2012-04-27 16:21:15 -07:00
c7d5f8b240
[issue #12 ] Add `bunyan.createLogger(OPTIONS)` form, as is more typical in node.js APIs.
...
This'll eventually become the preferred form.
2012-04-27 16:20:57 -07:00
6e0d1ecbc2
prep for future dev
2012-04-27 16:16:31 -07:00
6d9aa4ff5c
prepare for 0.6.9 release
2012-04-27 16:16:13 -07:00
8f1c8adcd7
color 'src' info red in default bunyan CLI coloring
2012-04-10 15:32:33 -07:00
ea39bf03a5
Bunyan CLI tweak to show an 'err' field that doesn't have a 'stack'.
2012-02-28 14:45:53 -08:00
fcbecef56e
prep for future dev
2012-02-27 16:48:22 -08:00
d4bbc707b1
prepare for 0.6.8 release
2012-02-27 16:48:12 -08:00
8ea2533620
Fix bad bug with the "fast child" path: `log.child({...}, true)`.
...
Timing impact. Before (numbers from my Mac):
$ node tools/timechild.js
Time `log.child`:
- adding no fields: 0.01307ms per iteration
- adding one field: 0.01336ms per iteration
- adding two fields: 0.0134ms per iteration
- adding serializer and one field: 0.01839ms per iteration
- adding a (stderr) stream and one field: 0.01905ms per iteration
- [fast] adding no fields: 0.000821ms per iteration
- [fast] adding one field: 0.001067ms per iteration
- [fast] adding two fields: 0.00122ms per iteration
After:
$ node tools/timechild.js
Time `log.child`:
- adding no fields: 0.01243ms per iteration
- adding one field: 0.01345ms per iteration
- adding two fields: 0.01343ms per iteration
- adding serializer and one field: 0.01671ms per iteration
- adding a (stderr) stream and one field: 0.01915ms per iteration
- [fast] adding no fields: 0.001742ms per iteration
- [fast] adding one field: 0.00193ms per iteration
- [fast] adding two fields: 0.002388ms per iteration
I.e., not great, but still 5x faster for the "fast child" path.
2012-02-27 16:46:57 -08:00
993f9d851b
prep for future dev
2012-02-24 12:20:05 -08:00
cfa6d92b8e
prepare for 0.6.7 release
2012-02-24 12:19:53 -08:00
9f8f6e77d2
changelog message for Mike's pull
2012-02-24 12:19:29 -08:00
a834151a31
prep for future dev
2012-02-23 21:20:58 -08:00
dd14781b6c
prepare for 0.6.6 release
2012-02-23 21:20:45 -08:00
9feb9c82bd
CLI file args: bunyan foo.log bar.log
2012-02-23 21:19:28 -08:00
77b99b6ef2
prep for future dev
2012-02-23 13:01:23 -08:00
d49bee3317
prepare for 0.6.5 release
2012-02-23 13:01:12 -08:00
887f407807
--no-color option
2012-02-23 13:00:53 -08:00
92a2e9d005
colored bunyan CLI output, and --color option
2012-02-22 21:03:03 -08:00
0f02707429
put 'level' field earlier in record
2012-02-22 10:53:12 -08:00
b52b1b60df
prep for future dev
2012-02-19 21:42:58 -08:00
d0fb9660c9
prepare for 0.6.4 release
2012-02-19 21:42:47 -08:00
40ec83b621
[issue #5 ] Fix `log.info() -> boolean` to work properly. Previous all were returning false.
...
Ditto all trace/debug/.../fatal methods.
2012-02-19 21:42:23 -08:00
39920c5785
prepare for 0.6.3 release
2012-02-16 16:53:13 -08:00
519f263ad1
Allow an optional `msg` and arguments to the `log.info(<Error> err)` logging form.
2012-02-16 16:49:19 -08:00
Trent Mick