Everybody knows it - you got a brand new shining appliance and if you look at monitoring?
Sending emails.
Or you should monitor software xyz on a AS400, a mainframe or what else?
SNMP? Negative. SSH? ditto. But sending emails is possible.
This is where mail2eventdb kicks in. mail2eventdb is implemented as agent for Netways EventDB.
mail2eventdb over mails directly from Postfix via pipe and prepare the mails in such a manner that sender, date sent, subject and content are clearly separated from each other.
Subsequent to that mail2eventdb loads the appropriate filter for the mail and prepares sender and/or content according to the filter and inserts it into the EventDB. The alerting itself will be done by check_eventdb.pl from the eventdb package..
mail2eventdb processes text-emails and MIME-emails. With MIME mail2eventdb can filter the content from text and HTML.
The concept was to have modular filter system so you can add arbitrary filters. mail2eventdb determines the name of the filter from assignments between mail-address/host-name and (optional) mail-address/application.
Furthermore mail2eventdb has a testmode for new filters, a collect mode to collect mails to get some stuff for testing and a logging function to log mails which could not be processed.
mail2eventdb was developed to process system-emails (Taperoboter, storage, appliances,...) and emails from any application able to send an email.
| Martin FürstenauMartin Fürstenau is a Senior System Engineer at Oce Printing Systems GmbH in Poing near Munich with the main focus in systems administration Linux/Unix and system monitoring and reporting.
He has over 20 years of experience in data center automation, system- and database administration and as a consultant and trainer.
He has over 5 years experience with Nagios and has developed a lot of plugins and extensions (c2n,handle_td_incident,mail2eventdb) for Nagios.
He is also the author of the main concept for the timeperiods enhancements of Nagios 3. His projects are published on monitoringexchange.org |
