TABLE 1: Available Monitoring Conditions
Condition	Notes
CPU threshold	Set warning and critical limits for CPU utilization over a sustained period. Best practice on an Exchange Server machine is to not exceed 80 percent of CPU utilization over 5 minutes.
Default Exchange 2000 services available	Monitor whether the standard set of Exchange 2000 services—IS, MTA, Routing Engine, System Attendant, World Wide Web Publishing, and SMTP Transport—are running. You can add to this list of services.
Free-space threshold	Set a warning and critical level for available space on a volume. You can set a separate condition for each volume that connects to the system. Typically, you want to monitor the volumes used for system binaries, Exchange Server databases, and Exchange Server trans-action logs.
SMTP Queues growth	Set thresholds for continuous queue growth for the SMTP virtual server. Given the speed of the Routing Engine and SMTP transport, queues aren't likely to accumulate over a sustained period. If messages are in the queue for longer than 5 minutes and you have a constant network link to other routing groups and servers, you probably have a problem with a connector.
Virtual memory threshold	Set warning and critical thresholds for available virtual memory. Don't let virtual memory fall below 25 percent free on an Exchange Server machine.
Win2K service available	You can monitor the availability of any Win2K service. For example, you can check to ensure that the IIS Admin service is always running or that a service that a third-party backup utility uses is available.
X.400 Queues growth	Set thresholds for continuous queue growth similar to the SMTP Queues growth condition, except that this condition pertains to the queues that the MTA maintains.