Conversation
* Swap out `winston` for `bunyan` * Monkey patch `console` so it always outputs to stderr * Add 'uncaughtException' handler and log exceptions as a fatal event before crashing the application. * Implement custom request logger similar to `connect.logger()`
The way the `console` object is constructed changed between v0.8 and v0.10. In the latest version of node the object is built from a constructor and conveniently has _stdout and _stderr properties which are references to streams which console will treat as stdout and stderr. In v0.8 the console object is a singleton by virtue of the methods being directly exported, and worse, the functions write to process.stdout and process.stderr directly.
And by that I mean I cobbled together a script (bin/messina.js) to shuttle log events off to a Graylog instance (ours happens to be called "loggins"). Note: It's mostly cobbled together by tearing apart the source of bunyan's CLI tool. I'd like to re-write it to be more testable.
* Makefile: `make` now starts the server and pipes stdout through bunyan to get readable logs * readme.md: update with information about the configuration environment variables necessary for bin/messina * [rename] bin/messina.js -> bin/messina
|
The Makefile has been updated so the default start server task automatically pipes through a formatter – just running The raw logs look like this The formatted logs look like this: When piping through
|
|
cc @jbuck ! |
|
Drats, the one big doh is that using Foreman, it adds about 19 characters to the line, and I have not yet found a good combination of cut, passing variables, and getting gelf working. foreman start -f Procfile|cut -c19- | GRAYLOG_HOST="loggins.mofoprod.net" GRAYLOG_PORT=12201 GRAYLOG_FACILITY="gelf" ./bin/messina that works!! Yeah, just not in upstart...yet. |
3 participants
Fixes #217