nolog | a node based event driven real time logfile parser | Runtime Evironment library

nolog is a JavaScript library typically used in Server, Runtime Evironment, Nodejs applications. nolog has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

nolog lets you watch (log)files in real time and matches patterns (regular expressions, functions, booleans) to events. ** New: now an npm package **. alternativly to $n(path) one can also write $n.watch(path). you can either watch a file (just pass a "path/to/file-string") or any readableStream (http, https, ...) see note: to test the included examples localy you might want to funnel your webservers logfiles to a local test.log. shout (throw an event) if a single logfile line matches an reguar expression. the pattern argument can either be a regular expression or a simple string ( means .*+?|()[]{}\ will be treated as 'normal' characters). shoutIfNot is the same (but opposite) of shoutIf - shoutIfNot throws an event if the pattern did not lead to a successfull match. shoutIf and shotIfNot start so called shout-jobs. si and sin are shortcuts for shoutIf and shoutIfNot. assign an event handler. on assigns an event handler to the NologEventEmitter listening for the eventname. shoutIf and shoutIfNot assigned events return an RegExp return array that's an array with a special index and input value. as there was nothing found at shoutIfNot the index value is null, the first value of the array is also null. input is the parsed log line. for other standard methods of NologEventEmitter see EventEmitter in the offical Node.js documentation kill a shoutIf or shoutIfNot job. no more googlebot events will be thrown. the shout-job with the name eventname gets killed. unwatch kills all shout-jobs (no more events get thrown) and stops the background task watching the specific file. killAll is a synonym for unwatch. if you kill the last last shout-job of a watched file, the file is automatically unwatched. said that, the NologEventEmitter object is still valid, if you add a new shout-job, the file is automatically re-watched. (think: magic). shout is fluffy shortcut for shoutIf. basically it shout throws an event with the name eventname if a case-iNsEnSeTiVE match for eventname was found. the NologEventEmitter attributs and methods can be also passed as an object via the watch method. additonally to the success event 'bot' another event is thrown, namely '!bot' if the pattern was not matched. this means, for evey parsed logline an event -either eventname or !eventname - is thrown. this is not the same as shoutIfNot - shoutIfNot throws a success match, if something was not matched. as a matter of fact, shoutIfNot also supports enableNotEvent. if the logline does not match the '/bot/i' the event 'human' is thrown. if the logline matches the event '!human' is thrown. (note: notEvents are less confusing when used with shoutIf). si and sin (and their longer worded aliases shoutIf and shoutIfNot) also support booleans patterns. the data value will always be a RegExp return array. si and sin (searchIf and searchIfNot) can also handle function patterns. the return value of the function pattern gets returned to the event callback. note: function patterns do not make too much sense with sin or notEvents, as the return value will always be a falsy value.