|Chapter 10 - Monitoring Exchange|
|Monitoring and Managing Microsoft Exchange 2000 Server|
|by Mike Daugherty|
|Digital Press 2001|
Monitoring is the use of automated processes to continually collect and analyze the operation of critical Exchange services. Monitoring is an important part of delivering high-quality messaging service and for achieving commitments of service level agreements. The overall goal of monitoring is to avoid possible service outages by predicting problems and by quickly noticing problems that cannot be predicted . This can be accomplished by either continually polling the monitored component or by receiving or detecting events from these components .
When the monitoring tool detects a problem, it should automatically alert the Exchange operations staff and provide immediate information regarding the nature and severity of the problem. Ideally, the monitoring tools should also be able to react to certain detected problems and initiate automatic recovery procedures.
Although Windows 2000 and Exchange 2000 provide some monitoring tools as part of the standard product set, this is an area where most enterprises choose third-party tools to augment the standard tools. Third-party tools generally provide monitoring capability for more than just Exchange. For example, NetIQ can monitor Exchange, Windows 2000, SQL, IIS, and other Microsoft BackOffice products. When considering any alternative tools it is recommended that you review not only your requirements for monitoring the Exchange environment, but also for monitoring the underlying services, such as the operating system.
Monitoring is performed for many different reasons, including:
Monitoring overall system health.
Monitoring components to detect and predict trends.
Monitoring to detect nondelivery of messages.
Monitoring the backup process.
Monitoring anti-virus software.
Monitoring the underlying network.
This chapter describes some of the monitoring tasks that should be performed.