If you're putting event data in databases, reduce your usual logs first with antilog, so the borring regular stuff doesn't appear.
Conversely, if certain things should appear, check for them and log an "expected event missing" entry.

Think of the DB as a history of exceptions in a"management by exceptions" scheme.

--dave
[See also antilog, http://datacenterworks.com/stories/antilog.html and http://sourceforge.net/projects/antilog/]


On 10/29/2014 08:40 AM, Dave Cramer wrote:
Is there anything out there that is written simply ? By this I mean I don't want to have to install a framework or a jvm or any large dependencies. Ideally this would be written in bash or the like.

The goal is to monitor cron jobs using something other than mail. 

Dave Cramer



---
GTALUG Talk Mailing List - talk@gtalug.org
http://gtalug.org/mailman/listinfo/talk



-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net           |                      -- Mark Twain