|
in reply to Re: Tripwire: A Tool For Intelligent Parsing of Syslog Messages
in thread Tripwire: A Tool For Intelligent Parsing of Syslog Messages
Sorry. I guess I should have made it clear--The code I've written doesn't legally belong to me. It was written on my employer's time, with my employer's workstation, after all. I can't share it.
What is free, however, is the description--from which a working model can be built and expanded upon.
The engine code weighs in at a little over 300 lines, and could probably be done in less space than that. All that's needed from there is a database to hold a list of inclusions, a list of exclusions, and the messages themselves the engine will use both to operate upon.
|
Re^3: Tripwire: A Tool For Intelligent Parsing of Syslog Messages
by Sinistral (Monsignor) on Jan 03, 2014 at 13:58 UTC
|
Could you provide more details?
This does sound like something that would be good for monitoring automated scripts and processes that now send emails where I work. Could you expand on how this system differs from Nagios and related tools? Nagios uses (perhaps completely custom) scripts and tools to provide a status, and am pretty sure has the ability to store historical data in MySQL. It's default display also looks similar to your display board, with indicators of green/yellow/red. Understand, I'm not trying to be one of those people saying "why did you do this when you could have used X", I'm trying to think how your system differs, so that if I can get time to do an implementation at my own work, I don't end up recreating Nagios (badly). | [reply] |
|
|
Are you referring to Tripwire (syslog parser) or Monolith (status dashboard) ...? From the sound of your question, I think you're talking about Monolith... in which case i'll reply to you on that thread.
| [reply] |
|
