Opensource Web Site Software Worth Considering
Blogs
b2evolution
Nucleus
WordPress
Classifieds
Noahs Classifieds
Content Management
Drupal
Geeklog
Joomla 1.5
b2evolution
Nucleus
WordPress
Noahs Classifieds
Drupal
Geeklog
Joomla 1.5
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.
| Web Serivces EJB Monitor | ||
|---|---|---|
| Module | Status | |
| real.time.volumes | OK | |
| universe.ejb | OK | |
| email.ejb | OK | |
If the status error changes from OK to ERROR on any of those three, then it will send an error.
nsca - Daemon and client program for sending passive check results across the network
nrpe - Daemon and plugin for executing plugins on remote hosts
| Overview: | Allows you to execute plugins on remote hosts in a relatively easy and transparent manner. | ||||||
| Files: |
|
||||||
| Description: |
This addon is designed to provide a way for executing plugins on a remote host. The check_nrpe plugin runs on the Nagios host and is used to send plugin execution requests to the nrpe agent on the remote host. The nrpe agent will then run an appropriate plugins on the remote host and return the plugin output and return code to the check_nrpe plugin on the Nagios host. The check_nrpe plugin then passes the remote plugin's output and return code back to Nagios as if it were its own. This allows for a rather transparent method of executing plugins on remote hosts. The nrpe agent can either be run as a standalone daemon or as a service under inetd. |
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.
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.