|
Tembria Server Monitor Menu
= Introduction and Overview= 100% Agentless Monitoring = Screenshots and Videos = Dashboards = Event Monitors = Notifications = System Requirements = Download Now Step-by-Step Evaluation
= Installation= Adding Network Devices = Adding Event Monitors = Sending Notifications = Viewing Dashboards = Viewing Reports = Advanced Topics Resources
= Pricing and How to Order= Scenarios = 1. Monitoring Critical Servers = 2. Finding Bandwidth Hogs = 3. Detecting Rogue Machines = 4. Monitoring Event Logs = 5. Monitoring Through VPNs = 6. Monitoring Through Firewalls = 7. Monitoring Switches w/ SNMP = FAQs = Version History |
Tembria Server Monitor - Monitoring Critical ServersScenario Summary: To monitor critical servers, ping and http event monitors were used with escalating levels of notifications. Scenario 1: Monitoring Critical Servers At a customer's site there are a set of critical machines which have an impact on operations if they are unavailable. Tembria Server Monitor was purchased and installed in order to generate immediate notifications if any of the critical servers are not responding. The Ping event monitor was configured to check each of 50 servers every 5 seconds and notifications are sent if a machine is unreachable or if the ping response time is more than 250 milliseconds. To avoid warning about transient ping failures, the option to not warn if one ping fails was selected. Notifications were configured so that all failures are written to the event history. After three failures in a row e-mail notifications are sent out to a group of selected network administrators. After ten failures in a row alphanumeric pages are set out as well. A web-based application running on the company's intranet server provides valuable information for the company's call centre. Tembria's HTTP event monitor was used to monitor key pages, check the information that they display and warn if an error is detected. A second instance of the HTTP event monitor was used to check the application's search feature and warn if the time to deliver results exceeded two seconds. Back to Scenarios List |
|
| copyright(c) 2003-2010, all rights reserved | ||