'syslog.h' bindings with a revised console module
This fork is being used as a stopgap while the main repo is updated for node 0.10.*
C bindings to syslog and a fast, more feature-rich console module.
$ npm install rconsole
By default your syslogs will land in
/var/log/messages. Add a new
facility where your syslog configuration is located to change this. (see notes)
Here is an example webserver that pipes
express.logger to the stream for notice severity logs. It includes
production configuration. Create a new file called
app.js with the following code:
var express =app = expressappappapp// pass in the stream to console.noticeappappappconsole
Start the server
$ node app.js
And then visit http://localhost:3000/ and express.logger will be streaming to
console.notice in your terminal as well as syslog.
To disable the stderr stream, start the app with
NODE_ENV=production and then
tail -f /var/log/path/to/logFile to monitor the logs
$ NODE_ENV=production node app.js
consoleconsoleconsoleconsoleconsoleconsoleconsoleconsoleconsoleconsoleconsoleconsoledir 'level 7': 'deep': 'level': 'inspect': true true 5consoleconsole
facilitychange the facility (syslog, default: user)
titlechange the title of the process (syslog, default: node)
showLineautomatically add line numbers (default: true)
showFileautomatically add file names (default: true)
showTimeautomatically add timestamps (default: true)
syslogHashTagsautomatically append hashtags for log analyzation (syslog, default: false)
highestLevellimit the display based on severity (default: debug)
showTagsadd tags with colors (stderr/stdout, default: true)
stderruse stderr (default: true)
stdoutuse stdout (default: false)
sysloguse syslog bindings (default: true)
The default configuration is suited for development, however you should immediately set up configuration for syslog and choose a facility (local0-local7) that is not already in use on your system.
By default your syslogs will land in
/var/log/messages with facility
user and tag
node. Configure a new
/etc/syslog-ng.conf or wherever your syslog configuration is located.
For rsyslog your configuration might look something like this:
local0.notice /var/log/node/production.loglocal0.info /var/log/node/staging.loglocal0.debug /var/log/node/debug.log
rconsole provides display features and is a drop in replacement for the native
console will come with a number of options that you can
console.set (see the api)
If you completely disable stderr/stdout you can just tail your syslogs.
The aim of this module is to provide an interface to
syslog.h based on the syslog RFC (http://tools.ietf.org/html/rfc5424). Any configuration that can be done with rsyslog or syslog-ng is not provided in this module; such as log reception, forwaring, filtering, etc. The archival destinations are not visible to or configurable by the app, and instead are completely managed by the execution environment.
(The MIT License)
Copyright (c) 2012 Thomas Blobaum email@example.com
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.