Alert Types to setup in Nagios

a.  Regular Expression HTTP monitor

We need the ability to monitor a part of a page.   The content needs to be able to match content on a page using regular expressions.  Also needed is the ability to log into the page.  Example of expression: /Temp_P18.*\n.*\n.*;(.*) Deg. C.*\n.*\n.*\n.*;(.*) %/

We need to be able to catch the values in the "()" areas listed above and check against those values.

We're experiencing issues with some monitors giving a HTTP-FORBIDDEN issue with the check_http scripts.


Monitoring Strategy and Architecture

In the attached child pages is information about IT Monitoring at Nu Skin.  This includes both the current state of monitoring, some research on best practices and a strategy for where we should take monitoring.  We want to move to more of a model where we manage to service levels not just responding to outage events.

Executive Summary

  1. Nu Skin has too many monitoring tools
  2. Nu Skin needs to have a better coordinated monitoring effort across groups
  3. Nu Skin can reduce the annual labor and maintaince of monitoring tools by migrating off of some tools.
  4. Nu Skin should enlist consultants to help clean up our monitoring, but should not spend a bunch more money on license for new tools.

Gartner Recommendations on IT Event Monitoring

Large enterprises should consider a multitier event management hierarchy, pushing some event processing and correlation out to the managed IT element at the bottom of the hierarchy to reduce the overflow of unnecessary events, using specialized event management tools to gain additional depth in specific IT domains at the middle tier of the hierarchy, and placing a general purpose manager of managers (MoMs) product at the top tier of the architecture to achieve a single, integrated view of events from a wide range of IT infrastructure elements.