What is Nagios ServiceNow Integration?
Nagios is probably the most popular monitoring tool in existence. It’s free, and has a large variety of plug-ins available. Although it may lack some bells and whistles (Gartners words, not not mine), by pairing it with a solid Event Management solution it can be very effective. At the end of the day, Nagios is an industry standard and is ‘getting the job done’ in thousands of enterprise environments. Couple that with the growing number of ServiceNow customers and you’ll understand the need for a powerful Nagios ServiceNow Integration.
The Nagios Event Integration for Evanios Operations allows Nagios to send critical events to Evanios Operations, which is our enterprise event management application that runs inside the ServiceNow cloud. Once in Evanios Operations, the events can be deduplicated, changed, correlated, analyzed, and used to trigger meaningful incidents or corrective automation.
The integration architecture is relatively simple. Nagios can run a command when an event occurs. Evanios provides a shell script called eops_handler.sh that will be called by Nagios. This shell script will package up script variables, and submit in a defined format to the Evanios command line client, which will handle submission to Evanios Operations.
For more information on how the integration works, and to learn how to set it up, see our integration documentation wiki
Why use Evanios for Nagios ServiceNow Integration?
Evanios is an event and operations management solution that runs directly on the ServiceNow. It acts as a “manager of managers”, collecting event data from all monitoring solutions. Events can be consolidated into a single pane of glass for an overall view of IT health. From there, events can be deduplicated and correlated, and decisions can be made (automatically) about which events should become incidents or trigger automation.
Since our Event Management solution is a ServiceNow application, we have the benefit of being able to leverage ITSM data from other applications. We can change our response to an event based on it’s definition the CMDB, or what business services it might impact. We can also respond differently if we’re in the middle of an active scheduled change. (It’s never fun to wake up on-call personnel for a scheduled change)
By putting an Event Management layer between the monitoring systems and ServiceNow’s incident application, it provides an effective way to eliminate the creation of bogus tickets in the service desk, and create smarter, more meaningful incidents. There are lots of other reasons to implement Event Management – the Event Management process defined in ITIL v3 Service Operation is a good read. Add it up and you can understand why Evanios is the best choice for Nagios ServiceNow Integration.