Other Means to Send Alerts
Other Means to Send Alerts
Hello! I am new to this forum and to Nagios but I am not new to monitoring. I work for a fairly large corporation and we currently use BMC products for our monitoring with other vendor specific tools. All of these tools funnel into and Event Management System. Some of these tools send traps via SNMP and other s initiate TCP connections into various adapters listening for these type of events. What I am curious about is if Nagios XI has a plugin or how-to article on getting Nagios to send SNMP Traps when an alerting condition happens or if Nagios XI has a way of executing a custom script by passing or piping variables into a custom command of ours. Email alerts will not work in our environment and we need something a little more enterprise friendly
Re: Other Means to Send Alerts
By design Nagios(and thus NagiosXI and even NagiosXI on top of Nagios) executes scripts for all of it's various interactions. The core of Nagios executes applications(called check plugins) based on a schedule that's created based off how service objects are configured. The Command's return code and data is entered into various logs and memory arrays that are periodically flushed to disk. Based on the state of this array, the object definitions for the service, it's contacts and the contact's notification settings: Nagios will execute another application(called a notification handler). There are also command handlers for events that can be used to more closely interact with service changes and the ability to write another type of daemon that ties closely into every little thing Nagios does(I just forget what it's called off the top of my head).
As Nagios is vary basic in it's design it relies heavily on a plentiful collection of scripts that make up the bulk of it's application code. Since the API is based of POSIX conventions the code is written is all sorts of different languages. These may both sound like cons, but they have always proven to be a great advantage.
As for sending SNMP traps, this would be vary easy to implement. However I'd love to hear more about how you would plan to integrate this
, Nagios doesn't have a MIB file so wouldn't you have to write one for your application? Even if you were able to, obviously there are ppl who know how, why then would this solution be enterprise friendly? It sounds to me like you would be engineering your own solution from scratch using a protocol designed to work with light-wight/embedded and real time systems. This doesn't sound ideal at all, wouldn't you be better off using SSL(or plain TCP) with a custom text or XML based protocol that you would be better able to interact with?
We also have a generic check result passing solution called NSCA that would be better suited for passing check results to another server. It does expect to communicate with a Nagios daemon, however as explained previously the Nagios daemon is vary simple and implementing this part of it would consist of listening on a FIFO(It's another term for reading a file) and parsing out commands one per line.
As Nagios is vary basic in it's design it relies heavily on a plentiful collection of scripts that make up the bulk of it's application code. Since the API is based of POSIX conventions the code is written is all sorts of different languages. These may both sound like cons, but they have always proven to be a great advantage.
As for sending SNMP traps, this would be vary easy to implement. However I'd love to hear more about how you would plan to integrate this
, Nagios doesn't have a MIB file so wouldn't you have to write one for your application? Even if you were able to, obviously there are ppl who know how, why then would this solution be enterprise friendly? It sounds to me like you would be engineering your own solution from scratch using a protocol designed to work with light-wight/embedded and real time systems. This doesn't sound ideal at all, wouldn't you be better off using SSL(or plain TCP) with a custom text or XML based protocol that you would be better able to interact with?We also have a generic check result passing solution called NSCA that would be better suited for passing check results to another server. It does expect to communicate with a Nagios daemon, however as explained previously the Nagios daemon is vary simple and implementing this part of it would consist of listening on a FIFO(It's another term for reading a file) and parsing out commands one per line.
Re: Other Means to Send Alerts
Your request will be simply done using Nagios. You can create event handler to send custom snmp traps or whatever your event management can accept. once event handler set up, if any of your host/service status in Nagios went warning or critical, it will run the event handler.