Introduction to server manager monitoring

In a four-tier environment, you can monitor critical event data and optionally receive notification when critical events exceed specified thresholds. This information is useful for determining the cause of an issue, thereby indicating corrective action. Critical events can be monitored for the following elements of the Teamcenter system: Web tier Monitor web tier server events such as abandoned servers, no servers available, and so forth. Server pool Monitor pool manager events such as login time, server crashes, and various types of server time-outs. Teamcenter servers Monitor server events on specific Teamcenter servers such as out of memory errors, long running queries, and memory use. File Management System (FMS) components Monitor Multi-Site events such as global memory pool events, route events, and ticket events. Translation components Monitor translation events such as dispatcher client events, dispatcher scheduler events, and dispatcher module events. You should review all monitoring settings, ensuring the thresholds are set correctly for your site. If you do not know the optimum monitoring setting for any given critical event, set the value to Collect. Collect the data and review to determine normal activity levels. Then set threshold values slightly higher than normal activity levels. You can configure monitoring behavior either temporarily in an interactive administrative interface, or persistently in XML configuration files. Both configuration methods require you to first define the EmailResponder element (specifying how and where email notification is set) and the LoggerResponder element (where critical event data is logged). You can then set values for the different types of critical events of which you want to be notified. You can control the frequency of email notifications and event logging by specifying suppression periods. Example You have configured the monitoring of business logic server crashes to send email notification when server crashes exceed 10 in 600 seconds. At 10:00, you set suppression of this notification to 4 hours. At 10:05, the notification threshold is met. Email notification is sent. The suppression clock starts to count down. The notification threshold is reached 22 times between 10:20 and 13:50. Notification is suppressed each time. At 14:00 the suppression clock reaches it 4-hour threshold. Another notification threshold is met for business logic server crashes at 14:20. Email notification is sent. Once again, the suppression clock starts.