articleHow to monitor Exchange with up.time


Monitoring the Network

The most critical component of any application is the network that surrounds it. To ensure that your network is available and running smoothly, we suggest monitoring the following components around your Exchange server:

  • Monitor the network switches, routers and firewalls that are between your users and your Exchange services.
  • Use the DNS service monitor to ensure your mail server name is resolving correctly.
  • Use the PING service monitor to ensure that your mail server is responding to network requests.

Monitoring Exchange

In this section we will review the monitors that are generally recommended to fully monitor your services.

Monitoring Exchange Performance

We recommend using the service monitors listed below to monitor the internal application performance of your Exchange Server.

  • Exchange Service Monitor. The Exchange service monitor provides detailed internal performance information from your Exchange Server. We recommend adding this service to your Exchange server (note: click the Save for Graphing checkbox beside each statistic in the service monitor if you want to be able to graph or report on internal performance at a later date). Please see the Microsoft Exchange Performance Metrics article for a full list of metrics available from the Exchange service monitor. The following graph shows an example of Exchange performance statistics collected from an existing Exchange service monitor:

    An example of some important Exchange Monitor settings and thresholds:

    NOTE: Many thresholds within the Exchange service monitor will depend on the size and usage of your Exchange server. We suggest enabling the Save for Graphing option on each statistic and then letting the monitor collect data for 2 to 3 days. After that time, review the collected data to see how each statistic has trended over time, and pick thresholds that seem appropriate to your installation.

  • Performance Service Monitor. The Performance service monitor allows you to monitor the average CPU consumption of your critical Exchange processes over time. We suggest that each Exchange process have a Performance monitor dedicated to it. Each process should not consume more than an average of 70% of system CPU for a period greater than 15 minutes. Here are some example settings for the Performance service monitor:

Monitoring Exchange Services

  • Windows Service Check Monitor. This monitor can be used to ensure that all required Exchange services are up and running on your server. In some cases you will not require all of these checks but we recommend configuring a Windows Service Check for each service named below. Each service should be in the running state.

    Windows Service Name Application
    Microsoft Exchange Event Exchange Event Controller
    Microsoft Exchange IMAP4 IMAP Email Service
    Microsoft Exchange Information Store Primary mailbox store service
    Microsoft Exchange Management Exchange WMI Managemnt Interface
    Microsoft Exchange MTA Stacks Provides Exchange X.400 services.
    Microsoft Exchange POP3 Provides POP version 3 services.
    Microsoft Exchange Routing Engine Mail Topological Routing Information Service
    Microsoft Exchange Site Replication Service Replicated Mail Server Synchronization Service
    Microsoft Exchange System Attendant Exchange Maintenance Service

    An example Windows Service Check monitor for the Microsoft Exchange Information Store is provided below. We recommend creating a similar service monitor for each of the Windows services above.

  • Process Count Monitor. The up.time Process Count monitor can be configured to ensure that Exchange processes are present on the host system. We recommend setting thresholds that alert if 0 instances of the processes in the table below are found.

    Process Name Application Details
    store Exchange Event Controller '.exe' not required for Windows Processes
    exmgmt Exchange Management Service '.exe' not required for Windows Processes
    mad General Exchange Service Process '.exe' not required for Windows Processes

    Here are some example settings to check for the store.exe process:

  • Windows Event Log Monitor. Exchange forces most error messages to the Application and System event logs. Unfortunately there are over 20 different source categories for Exchange errors. The table below indicates some of the most important event sources to monitor with the Windows Event Log monitor. We recommend configuring a monitor for each source with an event type of Error. We also suggest creating Event Log monitors for the System event log since System errors are very likely to indirectly impact your Exchange services.

    Log Type Source Name Event Type
    Application MSExchangeAL Error
    Application MSExchangeIS Error
    Application MSExchangeSA Error
    Application MSExchangeTransport Error
    Application POP3Svc Error

    Here are some example settings to check for error messages from the MsExchangeAL source:

Other Monitoring Considerations

  • SMTP, IMAP & POP Service Checks. To ensure basic availability of each of these services, please reference How to monitor e-mail Services (IMAP, POP, SMTP) with up.time.

  • User Authentication. up.time includes both Active Directory and LDAP service monitors to help ensure that the central authentication server is available.

  • Exchange Web Mail. If your users depend on Exchange Web Mail, you should also monitor the following components:

    • Monitor the Web Mail User Interface with the HTTP service monitor.
    • Monitor the World Wide Web Publishing Service with the Windows Service Check monitor.
    • Monitor the IIS Admin Service with the Windows Service Check monitor.
    • Monitor the w3wp.exe process for performance using the Performance monitor, and availability using the Process Count monitor.
    • Monitor the inetinfo.exe process for peformance using the Performance monitor, and availability using the Process Count monitor.

Monitoring the Host Server

Don't forget the value of monitoring the server that is hosting your Exchange Mail Services. Monitoring and alerting on the performance of your servers will be critical to ensure that you maintain server availability and meet capacity demands. Monitoring key performance indicators such as CPU Usage, Disk I/O, Network I/O and Memory usage is essential to ensure your servers are running properly.

Next Steps

Now that you are monitoring your Exchange Server, it is time to move on to one of these next steps:

  • Report Service Outages & Availability.
  • Group monitors into an Application.
  • Apply monitoring templates to many systems using Service Groups.

Monitor Reference

The following service monitors were used in the monitoring example:

Related Articles

Microsoft Exchange Performance Metrics


This article outlines the performance metrics that up.time collects from a Microsoft Exchange server.

By: uptime Support | Date Created: 1-26-2007 | Last Modified: 6-30-2011 | Index: 132


Configuring up.time to send alerts with a hosted Exchange server


If you are using an online hosted Exchange email server and would like to configure up.time to use this email server, you will also need to set up a local email server to relay the up.time...

By: uptime Support | Date Created: 8-31-2011 | Last Modified: 9-1-2011 | Index: 558


How to monitor IMAP, POP & SMTP email services


Monitoring email servers can be a complex project. In this How To article we review critical components and metrics that you should monitor to ensure your email services are running optimally and...

By: uptime Support | Date Created: 5-18-2007 | Last Modified: 6-29-2011 | Index: 174


Windows Event Log Monitor returns Output: Monitor failed: For inp...


This error indicates that the target agent server's up.time agent is incompatible with your monitoring station version. Please upgrade the agent on the impacted server and verify that this error is...

By: uptime Support | Date Created: 8-26-2010 | Last Modified: 8-10-2011 | Index: 497


Is Performance Monitor Interface required to monitor WebSphere?


Yes, up.time utilizes the information provided by pmi in order to produce performance graphs so it is required to be installed on the target WebSphere server.

By: uptime Support | Date Created: 8-20-2010 | Last Modified: 8-10-2011 | Index: 492


User Comments

No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement