Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 206 lines (135 sloc) 7.231 kB
135163e @trentm VERSIONS, cutarelease prep
authored
1 # bunyan Changelog
2
13b36fb @trentm prep for future dev
authored
3 ## bunyan 0.7.1 (not yet released)
4
4f28afc @trentm note it
authored
5 - jsstyle'ing (via `make check`)
13b36fb @trentm prep for future dev
authored
6
7
2daf47c @trentm prepare for 0.7.0 release
authored
8 ## bunyan 0.7.0
6e0d1ec @trentm prep for future dev
authored
9
c7d5f8b @trentm [issue #12] Add `bunyan.createLogger(OPTIONS)` form, as is more typic…
authored
10 - [issue #12] Add `bunyan.createLogger(OPTIONS)` form, as is more typical in
11 node.js APIs. This'll eventually become the preferred form.
6e0d1ec @trentm prep for future dev
authored
12
13
6d9aa4f @trentm prepare for 0.6.9 release
authored
14 ## bunyan 0.6.9
fcbecef @trentm prep for future dev
authored
15
8f1c8ad @trentm color 'src' info red in default bunyan CLI coloring
authored
16 - Change `bunyan` CLI default output to color "src" info red. Before the "src"
17 information was uncolored. The "src" info is the filename, line number and
18 function name resulting from using `src: true` in `Logger` creation. I.e.,
19 the `(/Users/trentm/tm/node-bunyan/examples/hi.js:10)` in:
20
21 [2012-04-10T22:28:58.237Z] INFO: myapp/39339 on banana.local (/Users/trentm/tm/node-bunyan/examples/hi.js:10): hi
22
ea39bf0 @trentm Bunyan CLI tweak to show an 'err' field that doesn't have a 'stack'.
authored
23 - Tweak `bunyan` CLI default output to still show an "err" field if it doesn't
24 have a "stack" attribute.
25
fcbecef @trentm prep for future dev
authored
26
d4bbc70 @trentm prepare for 0.6.8 release
authored
27 ## bunyan 0.6.8
993f9d8 @trentm prep for future dev
authored
28
8ea2533 @trentm Fix bad bug with the "fast child" path: `log.child({...}, true)`.
authored
29 - Fix bad bug in `log.child({...}, true);` where the added child fields **would
30 be added to the parent's fields**. This bug only existed for the "fast child"
31 path (that second `true` argument). A side-effect of fixing this is that
32 the "fast child" path is only 5 times as fast as the regular `log.child`,
33 instead of 10 times faster.
34
993f9d8 @trentm prep for future dev
authored
35
cfa6d92 @trentm prepare for 0.6.7 release
authored
36 ## bunyan 0.6.7
a834151 @trentm prep for future dev
authored
37
9f8f6e7 @trentm changelog message for Mike's pull
authored
38 - [issue #6] Fix bleeding 'type' var to global namespace. (Thanks Mike!)
39
a834151 @trentm prep for future dev
authored
40
dd14781 @trentm prepare for 0.6.6 release
authored
41 ## bunyan 0.6.6
77b99b6 @trentm prep for future dev
authored
42
9feb9c8 @trentm CLI file args: bunyan foo.log bar.log
authored
43 - Add support to the `bunyan` CLI taking log file path args, `bunyan foo.log`,
44 in addition to the usual `cat foo.log | bunyan`.
45 - Improve reliability of the default output formatting of the `bunyan` CLI.
46 Before it could blow up processing log records missing some expected
47 fields.
48
77b99b6 @trentm prep for future dev
authored
49
d49bee3 @trentm prepare for 0.6.5 release
authored
50 ## bunyan 0.6.5
b52b1b6 @trentm prep for future dev
authored
51
92a2e9d @trentm colored bunyan CLI output, and --color option
authored
52 - ANSI coloring output from `bunyan` CLI tool (for the default output mode/style).
53 Also add the '--color' option to force coloring if the output stream is not
887f407 @trentm --no-color option
authored
54 a TTY, e.g. `cat my.log | bunyan --color | less -R`. Use `--no-color` to
55 disable coloring, e.g. if your terminal doesn't support ANSI codes.
56 - Add 'level' field to log record before custom fields for that record. This
57 just means that the raw record JSON will show the 'level' field earlier,
58 which is a bit nicer for raw reading.
0f02707 @trentm put 'level' field earlier in record
authored
59
b52b1b6 @trentm prep for future dev
authored
60
d0fb966 @trentm prepare for 0.6.4 release
authored
61 ## bunyan 0.6.4
40ec83b @trentm [issue #5] Fix `log.info() -> boolean` to work properly. Previous all…
authored
62
63 - [issue #5] Fix `log.info() -> boolean` to work properly. Previous all were
64 returning false. Ditto all trace/debug/.../fatal methods.
65
66
39920c5 @trentm prepare for 0.6.3 release
authored
67 ## bunyan 0.6.3
38ea773 @trentm prep for future dev
authored
68
519f263 @trentm Allow an optional `msg` and arguments to the `log.info(<Error> err)` …
authored
69 - Allow an optional `msg` and arguments to the `log.info(<Error> err)` logging
70 form. For example, before:
71
72 log.debug(my_error_instance) // good
73 log.debug(my_error_instance, "boom!") // wasn't allowed
74
75 Now the latter is allowed if you want to expliciting set the log msg. Of course
76 this applies to all the `log.{trace|debug|info...}()` methods.
77
61ff403 @trentm clearer output for fields with spaces or empty string in bunyan cli o…
authored
78 - `bunyan` cli output: clarify extra fields with quoting if empty or have
79 spaces. E.g. 'cmd' and 'stderr' in the following:
80
81 [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")
82
38ea773 @trentm prep for future dev
authored
83
5e12452 @trentm prepare for 0.6.2 release
authored
84 ## bunyan 0.6.2
5361795 @trentm prep for future dev
authored
85
a14cea4 @trentm changelog for npm publish guard
authored
86 - Fix/guard against unintended inclusion of some files in npm published package
87 due to <https://github.com/isaacs/npm/issues/2144>
88
5361795 @trentm prep for future dev
authored
89
aa52789 @trentm prepare for 0.6.1 release
authored
90 ## bunyan 0.6.1
9c8f4e1 @trentm prep for future dev
authored
91
8c0e3ab @trentm npmignore to avoid crud in published packages
authored
92 - Internal: starting jsstyle usage.
93 - Internal: add .npmignore. Previous packages had reams of bunyan crud in them.
94
9c8f4e1 @trentm prep for future dev
authored
95
de2b661 @trentm prepare for 0.6.0 release
authored
96 ## bunyan 0.6.0
c12a90a @trentm issue #4: add 'pid' automatic log record field
authored
97
98 - Add 'pid' automatic log record field.
e8581c5 @trentm prep for future dev
authored
99
100
7f262ba @trentm prepare for 0.5.3 release
authored
101 ## bunyan 0.5.3
63f97b8 @trentm prep for future dev
authored
102
dda4603 @trentm mention 'client_req' in changelog
authored
103 - Add 'client_req' (HTTP client request) standard formatting in `bunyan` CLI
104 default output.
d531072 @trentm bunyan CLI output includes all keys
authored
105 - Improve `bunyan` CLI default output to include *all* log record keys. Unknown keys
106 are either included in the first line parenthetical (if short) or in the indented
107 subsequent block (if long or multiline).
108
63f97b8 @trentm prep for future dev
authored
109
768b2de @trentm prepare for 0.5.2 release
authored
110 ## bunyan 0.5.2
a8b054e @trentm prep for future dev
authored
111
9f5581b @trentm issue #3: more type checking of Logger ctor options and log.child opt…
authored
112 - [issue #3] More type checking of `new Logger(...)` and `log.child(...)`
113 options.
450e4eb @trentm start a test suite
authored
114 - Start a test suite.
115
a8b054e @trentm prep for future dev
authored
116
74f3787 @trentm prepare for 0.5.1 release
authored
117 ## bunyan 0.5.1
969ac69 @trentm prep for future dev
authored
118
3649708 @trentm note issue #2 for this
authored
119 - [issue #2] Add guard on `JSON.stringify`ing of log records before emission.
120 This will prevent `log.info` et al throwing on record fields that cannot be
121 represented as JSON. An error will be printed on stderr and a clipped log
122 record emitted with a 'bunyanMsg' key including error details. E.g.:
887f407 @trentm --no-color option
authored
123
1a0cd4b @trentm issue #2: Add guard on `JSON.stringify`ing of log records before emis…
authored
124 bunyan: ERROR: could not stringify log record from /Users/trentm/tm/node-bunyan/examples/unstringifyable.js:12: TypeError: Converting circular structure to JSON
125 {
126 "name": "foo",
127 "hostname": "banana.local",
128 "bunyanMsg": "bunyan: ERROR: could not stringify log record from /Users/trentm/tm/node-bunyan/examples/unstringifyable.js:12: TypeError: Converting circular structure to JSON",
129 ...
130
887f407 @trentm --no-color option
authored
131 Some timing shows this does effect log speed:
132
1a0cd4b @trentm issue #2: Add guard on `JSON.stringify`ing of log records before emis…
authored
133 $ node tools/timeguard.js # before
134 Time try/catch-guard on JSON.stringify:
135 - log.info: 0.07365ms per iteration
136 $ node tools/timeguard.js # after
137 Time try/catch-guard on JSON.stringify:
138 - log.info: 0.07368ms per iteration
3649708 @trentm note issue #2 for this
authored
139
969ac69 @trentm prep for future dev
authored
140
cb41c7e @trentm prepare for 0.5.0 release
authored
141 ## bunyan 0.5.0
543ef15 @trentm 'log.info(err)' support
authored
142
25b8eea @trentm Use 10/20/... instead of 1/2/... for level constant values.
authored
143 - Use 10/20/... instead of 1/2/... for level constant values. Ostensibly this
144 allows for intermediary levels from the defined "trace/debug/..." set.
145 However, that is discouraged. I'd need a strong user argument to add
146 support for easily using alternative levels. Consider using a separate
147 JSON field instead.
140c9fd @trentm s/service/name/ for Logger name field. "service" is unnecessarily tie…
authored
148 - s/service/name/ for Logger name field. "service" is unnecessarily tied
149 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
150 - Add `log.level(...)` and `log.levels(...)` API for changing logger stream
151 levels.
152 - Add `TRACE|DEBUG|INFO|WARN|ERROR|FATAL` level constants to exports.
543ef15 @trentm 'log.info(err)' support
authored
153 - Add `log.info(err)` special case for logging an `Error` instance. For
154 example `log.info(new TypeError("boom")` will produce:
155
156 ...
157 "err": {
158 "message": "boom",
159 "name": "TypeError",
160 "stack": "TypeError: boom\n at Object.<anonymous> ..."
161 },
162 "msg": "boom",
163 ...
141253c @trentm prep for future dev
authored
164
165
12f2701 @trentm prepare for 0.4.0 release
authored
166 ## bunyan 0.4.0
e934baf @trentm v0.4: add 'src' call source location info support (the Yunong release)
authored
167
168 - Add `new Logger({src: true})` config option to have a 'src' attribute be
169 automatically added to log records with the log call source info. Example:
170
171 "src": {
172 "file": "/Users/trentm/tm/node-bunyan/examples/src.js",
173 "line": 20,
174 "func": "Wuzzle.woos"
175 },
d7e499b @trentm prep for future dev
authored
176
177
7c94825 @trentm prepare for 0.3.0 release
authored
178 ## bunyan 0.3.0
6806112 @trentm - `log.clone` -> `log.child` to better reflect the relationship: stre…
authored
179
40777aa @trentm 'log.child(..., true)' support for 10x faster with 'simple' field add…
authored
180 - `log.child(options[, simple])` Added `simple` boolean arg. Set `true` to
181 assert that options only add fields (no config changes). Results in a 10x
887f407 @trentm --no-color option
authored
182 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
183 "fast child" creation takes about 0.001ms. IOW, if your app is dishing
184 10,000 req/s, then creating a log child for each request will take
185 about 1% of the request time.
6806112 @trentm - `log.clone` -> `log.child` to better reflect the relationship: stre…
authored
186 - `log.clone` -> `log.child` to better reflect the relationship: streams and
187 serializers are inherited. Streams can't be removed as part of the child
188 creation. The child doesn't own the parent's streams (so can't close them).
189 - Clean up Logger creation. The goal here was to ensure `log.child` usage
190 is fast. TODO: measure that.
191 - Add `Logger.stdSerializers.err` serializer which is necessary to get good
192 Error object logging with node 0.6 (where core Error object properties
193 are non-enumerable).
d123784 @trentm prep for future dev
authored
194
195
7798f40 @trentm prepare for 0.2.0 release
authored
196 ## bunyan 0.2.0
aecc04f @trentm prep for subsequent release
authored
197
a475a1a @trentm 0.2: specing core log record fields (mainly)
authored
198 - Spec'ing core/recommended log record fields.
199 - Add `LOG_VERSION` to exports.
200 - Improvements to request/response serializations.
aecc04f @trentm prep for subsequent release
authored
201
202
7539c03 @trentm prepare for 0.1.0 release
authored
203 ## bunyan 0.1.0
135163e @trentm VERSIONS, cutarelease prep
authored
204
205 First release.
Something went wrong with that request. Please try again.