Schedule demo

Exchange Server Monitoring


Exchange Server Versions Supported: Exchange 2019, Exchange 2016, Exchange 2013, Exchange 2010, Exchange 2007, Exchange 2003 and older versions.

Prerequisites for monitoring Exchange Server: Monitoring of Exchange Server is possible only if Applications Manager is running in a Windows System. Refer Prerequisites Section.

Using the REST API to add a new Exchange server monitor:Click here

Attributes Monitored: Refer Exchange Server Parameters to know more about the attributes monitored.

To create a Exchange Server Monitor, follow the given steps:

  1. Click on New Monitor link. Choose Exchange Server under Mail Servers.
  2. Enter a Display name for the new monitor that you're going to add.
  3. Enter the IP Address or hostname of the host in which the Exchange Server is running.
  4. Select Exchange Server Version - Exchange 2019, Exchange 2016, Exchange 2013, Exchange 2010, Exchange 2007, Exchange 2003 or below.
  5. Select the Server Role to be monitored.
  6. Choose the Exchange Server Services you want to monitor from the list.
  7. Select the Exchange Server Services you want to monitor.
  8. Provide the authentication details such as User Name, Domain Name, and Password for the system in which Exchange server is running.
  9. You can enter your own credential details or select preconfigured credentials details in Credentials Manager. If you wish to enter your own credentials, specify username and password details for the monitor.
  10. Choose the Mode of Monitoring - Powershell or WMI. By default, the connectionURI will be detected. If neccessary, it can be customized.
    Know more about using the Powershell option
  11. Enable the Use CredSSP Authentication option only if you want to fetch Exchange Queues metrics for non-mailbox roles in versions 2010 and above where the Applications Manager and Exchange server are in different domains. Know more about using CredSSP authentication
  12. Specify the timeout value in seconds. Value should be greater than 120 seconds. However, this is applicable only in Powershell mode of monitoring.
  13. Enter the polling interval time in minutes.
  14. If you are adding a new monitor from an Admin Server, select a Managed Server.
  15. Choose the Monitor Group from the combo box to which you want to associate the Monitor (optional). You can choose multiple groups to associate your monitor.
  16. Click Add Monitor(s). This discovers the Monitor from the network and starts monitoring them.

Know more about Exchange Server's component-specific performance counters that Applications Manager monitors.

Note: Monitoring of Exchange Server is possible only if Applications Manager is running on a Windows system. Exchange Monitoring now supports data collection in two ways:

  1. WMI
    • For users who have not installed/do not require Powershell
    • To choose this mode, select the WMI Mode of Monitoring in the new monitor page.
    • Mailbox and Database Statistics for Mailbox Server Role is not available for this setting.
  2. Powershell

Applications Manager allows you to efficiently monitor various versions of your Exchange Server, providing detailed reports on performance, availability, and the functioning of server roles. It centralizes the collection of Exchange component-specific performance counters, helping you detect issues, send alerts, and prevent potential service outages or configuration problems. Users can proactively manage Exchange Servers and identify issues before they become critical.

Applications Manager gathers data related to each of your Exchange Server Roles:

  • Mailbox Server Role - Monitor your mailbox and public folder databases and diagnose issues pertaining to all related messaging data.
  • Client Access Server Role - Monitor overall client access like ActiveSync, .NET, OWA, Web Services connections and hardware performance.
  • Unified Messaging Server Role - Track integrated dial-in access performance and monitor e-mail, voicemail, fax, calendar information and contacts.
  • Hub Transport Server Role - Monitor the mail flow, routing, and delivery within the Exchange organization and identify disk performance bottlenecks.
  • Edge Transport Server Role - Monitor EdgeSync services, Active Directory Application Mode, SMTP connection authentication, transport queue databases and logs.

Applications Manager supports monitoring of counters relevant to the following server roles:

Exchange Server - Monitored Parameters

Go to the Monitors Category View by clicking the Monitors tab. Click on Exchange Server under the Mail Servers Table. Displayed is the Exchange Server bulk configuration view distributed into three tabs:

  • Availability tab, gives the Availability history for the past 24 hours or 30 days.
  • Performance tab gives the Health Status and events for the past 24 hours or 30 days.
  • List view enables you to perform bulk admin configurations.
Mailbox Role CountersExchange Server Version
Attribute nameDescription20072010201320162019
POP & IMAP Connections
Current POP ConnectionsThe total number of POP connections opened since the computer was last started.
Current IMAP ConnectionsThe total number of POP connections opened since the computer was last started.
SMTP Connections
Inbound ConnectionsThe total number of currently inbound connections.
Outbound ConnectionsThe number of connections that were currently outbound.
Messages Sent/secThe rate at which outbound messages are being sent.
Messages Received/secThe rate at which inbound messages are being received.
Latency Requirements Counters
Database PageFault Stalls/secThe rate of page faults that can't be serviced because there are no pages available for allocation from the database cache. This counter should be 0 on production servers.
Database I/O Reads Average LatencyThe average time, in ms, to read from the database file. The average value should be below 200 ms. Maximum values shouldn't be higher than 1,000 ms.
Database I/O Writes Average LatencyThe average time, in ms, to write to the database file. This latency should be less than the MSExchange Database\I/O Database Reads (Recovery) Average Latency when battery-backed write caching is utilized.
I/O Log Reads/secThe number of times data was read from a log file. Specific to log replay and database recovery operations.
I/O Log Writes/secThe number of times a log buffer was written to the active log file. Specific to log replay and database recovery operations
Log Record Stalls/secThe number of log records that can't be added to the log buffers per second because the log buffers are full. The average value should be below 10 per second. Maximum values shouldn't be higher than 100 per second.
Log Threads WaitingThe number of threads waiting to complete an update of the database by writing their data to the log. The average value should be less than 10 threads waiting.
Message Queuing Counters
Mailbox Messages Queued For SubmissionThe current number of submitted messages not yet processed by the transport layer. The threshold value should be below 50 at all times. Shouldn't be sustained for more than 15 minutes.
Public Messages Queued For SubmissionThe current number of submitted messages not yet processed by the transport layer. The threshold value should be less than 20 at all times.
Message Queue Counters
Messages Currently Queued for DeliveryTotal number of messages currently waiting in all Exchange transport queues for delivery at a given point in time.
Messages Queued For Delivery/secRate at which messages are being queued for delivery across all Exchange transport queues, measured per second.
Information Store RPC Processing Counters
IS RPC RequestsThe number of client requests currently being processed by the RPC Client Access service.
IS RPC Averaged LatencyThe latency averaged for the past 1,024 packets (in ms).
Cache Statistics
Number Of Cache Active ConnectionsThe number of active connections in all data connection pools created for a specific PowerPivot service application instance.
Number Of Cache Idle ConnectionsThe number of idle connections in all data connection pools created for a specific PowerPivot service application instance.
Number Of Cache ConnectionsThe number of connections to the server stored in the cache.
Cache Total CapacityThe size of the cached server connection pool.
RPC Client Throttling & Client Activity Counters
Client RPC Average LatencyRPC Average Latency is server RPC latency, in ms, averaged for the past 1,024 packets. The threshold value should be less than 50 ms on average for each client.
RPC Client BackOff/secThe rate that the server notifies the client to back-off. Higher values may indicate that the server may be incurring a higher load resulting in an increase in overall averaged RPC latencies, causing client throttling to occur.
Client: RPCs Failed/secThe client-reported rate of failed RPCs since the store was started.
Client: RPCs FailedThe client-reported number of failed RPCs since the store was started.
Search Index Counters
% Processsor Time of indexingThe percentage of elapsed processor time that the Exchange Search Service is actively consuming across all CPUs at a given point in time.
Crawler Mailboxes RemainingThe number of mailboxes still remaining to be crawled by the Exchange Search indexer at the current point in time.
Content Indexing Counters
Percentage Processor Time of indexingThe amount of processor time being consumed to update content indexing within the store process. Full crawls increase overall processing time, but should never exceed overall store CPU capacity.
Average Document Indexing TimeThe average, in ms, of how long it takes to index documents. The threshold value should be less than 30 seconds at all time.
Full Crawl Mode StatusThis counter is used to determine if a full crawl is occurring for any specified database. Possible values are
  • 1 - going through a full crawl
  • 0 - not going through a full crawl
Average Latency of RPCs used to Obtain ContentThe average latency, in ms, of the most recent RPCs to the Information Store service. These RPCs are used to get content for the filter daemon for the specified database.
Crawler Mailboxes RemainingAny value of 1 or higher indicated the mailboxes in the database are being crawled but when the crawl is completed, the value is set to 0. 
Client-Related Search Counters
Slow Find Row RateThe rate at which the slower FindRow needs to be used in the mailbox store. The threshold value should be no more than 10 for any specific mailbox store. Higher values indicate applications are crawling or searching mailboxes, which is affecting server performance.
Search Task RateThe number of search tasks created per second. The threshold value should be less than 10 at all times.
Slow QP ThreadsThe number of query processor threads currently running queries that aren't optimized. The threshold value should be less than 10 at all times.
Slow Search ThreadsThe number of search threads currently running queries that aren't optimized. The threshold value should be less than 10 at all times.
Database Counters
Log Bytes Writes/secThe rate of bytes written to the log. The threshold value should be less than 10,000,000 at all times.
Database Cache Percent HitThe percentage of database file page requests fulfilled by the database cache without causing a file operation. If this percentage is too low, the database cache size may be too small. The threshold value should be over 90% for companies with majority online mode clients. The threshold value should be over 99% for companies with majority cached mode clients. If the hit ratio is less than these numbers, the database cache may be insufficient.
Database Cache Size in MBThe amount of system memory, in megabytes (MB), used by the database cache manager to hold commonly used information from the database files to prevent file operations. Maximum value is RAM-2GB. Use this counter along with store private bytes to determine if there are store memory leaks.
Version Buckets AllocatedThe total number of version buckets allocated. The threshold value should be less than 12,000. The maximum default version is 16,384.
Log Threads WaitingThe number of threads waiting for their data to be written to the log to complete an update of the database. If this number is too high, the log may be a bottleneck. The threshold value should be less than 10 on average. Regular spikes concurrent with log record stall spikes indicate that the transaction log disks are a bottleneck.
Log Generation Check Point DepthRepresents the amount of work in the log file count that needs to be redone or undone to the database files if the process fails. The threshold value should be below 500 at all times for the Mailbox server role. A healthy server should indicate between 20 and 30 for each database instance. If checkpoint depth increases continually for a sustained period, this indicates either a long-running transaction, or a bottleneck.
Database Instances I/O Reads Avg LatencyThe average length of time, in ms, per database read operation. The threshold value should be 20 ms on average.
Database Instances I/O Writes Avg LatencyThe average length of time, in ms, per database write operation. The threshold value should be 50 ms on average. Maximum values of up to 100 ms are acceptable if not accompanied by database page fault stalls.
Mailbox Assistant Counters
Percentage Processor Time of Mailbox AssistantPercentage Processor Time of Mailbox Assistant. The threshold value should be less than 5% of overall CPU capacity.
Average Event Processing Time in SecondsThe average processing time of the events chosen. The threshold value should be less than 2 at all times.
Events in QueueThe number of events in the in-memory queue waiting to be processed by the assistants. The threshold value should be a low value at all times. High values may indicate a performance bottleneck.
Events Polled/secThe number of events polled per second. Determines current load statistics for this counter.
Mailboxes Processed/secThe rate of mailboxes processed by time-based assistants per second. Determines current load statistics for this counter.
Resource Booking Counters
Average Resource Booking Processing TimeThe average time to process an event in the Resource Booking Attendant. High values may indicate a performance bottleneck.
Requests Failed in Resource BookingThe total number of failures that occurred while the Resource Booking Attendant was processing events. The threshold value should be 0 at all times.
Calendar Attendant Counters
Average Calendar Attendant Processing TimeThe average time to process an event in the Calendar Attendant. High values may indicate a performance bottleneck.
Requests Failed in Calendar AttendantThe total number of failures that occurred while the Calendar Attendant was processing events.The threshold value should be 0 at all times.
Store Interface Counters / Store Client Request Counters (for Exchange server 2007 and 2010)
RPC Latency AverageThe average latency, in ms, of RPC requests. The average is calculated over all RPCs since exrpc32 was loaded. The threshold value should be less than 100 ms at all times.
ROP Requests OutstandingThe total number of outstanding remote operations requests. Used for determining current load.
RPC Requests OutstandingThe current number of outstanding RPC requests.
RPC Requests Sent/secThe total number of outstanding RPC requests. Used for determining current load.
Percentage RPC Requests FailedThe percentage of failed requests in the total number of RPC requests. Failed means the sum of failed with error code plus failed with exception. The threshold value should be less than 1 at all times.
Percentage RPC Slow RequestsThe percentage of slow RPC requests among all RPC requests. A slow RPC request is one that has taken more than 500 ms. The threshold value should be less than 1 at all times.
HUB Servers in RetryThe number of Hub Transport servers in retry mode. The threshold value should be 0 at all times.
Successful Submission/secThe number of currently successful mail submission per second.
Failed Submission/secThe number of failed submissions per second.
Temporary Submission Failures/secThe number of temporary submission failures per second.
RPC Operations/secThe current number of RPC operations occurring per second.
Information Store Statistics / Information Store Counters (for Exchange server 2007 and 2010)
Client: RPC Operations/secThe number of RPC operations per second for each client type connection.
JET Log Records/secThe rate that database log records are generated while processing requests for the client. Used to determine current load.
JET Pages Read/secThe rate that database pages are read from disk while processing requests for the client. Used to determine current load.
Directory Access: LDAP Reads/secThe current rate that LDAP reads occur while processing requests for the client. Used to determine the current LDAP read rate per protocol.
Directory Access: LDAP Writes/secThe current rate that LDAP writes occur while processing requests for the client. Used to determine the current LDAP read rate per protocol.
Directory Access: LDAP Searches/secThe rate of LDAP search queries per second being made to Active Directory by the Exchange Information Store for a specific client type (e.g., MAPI, OWA, EAS) at a given point in time.
Messages Delivered/secThe rate that messages are delivered to all recipients. Indicates current message delivery rate to the store.
IS Messages Sent/secThe rate that messages are sent to transport. Used to determine current messages sent to transport.
IS Messages Submitted/secThe rate that messages are submitted by clients. Used to determine current rate that messages are being submitted by clients.
User CountThe number of users connected to the information store. Used to determine current user load.
Replication Receive Queue SizeThe number of replication messages waiting to be processed.

Note: The metrics under the Mailbox and Database Statistics Counters tab marked with * are only supported in Applications Manager version 172900 and above.

Mailbox and Database Statistics CountersExchange Server Version
Attribute nameDescription20072010201320162019
Top Mailboxes
Mailbox User NameUsername of the Exchange Mailbox User.
Warning Quota Utilization*The percentage of mailbox storage used relative to the warning quota set for the user's mailbox (in %).
Prohibit Send Quota Utilization*The percentage of mailbox storage used relative to the Prohibit Send Quota limit (in %).
Prohibit Send and Receive Quota Utilization*The percentage of mailbox storage used relative to the Prohibit Send and Receive Quota limit (in %).
Total Mailbox SizeThe total amount of storage space occupied by the user's mailbox (in MB).
Number of ItemsSpecifies the number of items in mailbox.
Warning Quota *Storage limit set for a mailbox (in MB). A warning message will be received when the mailbox size exceeds the specified limit.
Prohibit Send Quota*Storage limit set for a mailbox after which the user is prohibited from sending any new emails (in MB).
Prohibit Send and Receive Quota*Storage limit set for a mailbox after which the user is prohibited from both sending and receiving emails (in MB).
Last Logon Time*Time of last login by the mailbox user.
Use Database Quota Defaults*Allows mailboxes to inherit storage quota settings from the database level.
Inactive Mailbox Users
Mailbox User NameUsername of the Exchange Mailbox User.
Last Logon TimeTime of last login by the mailbox user.
Days since Last Login*Number of days that have passed since the user last logged into their mailbox.
Database Statistics (2010, 2013, 2016 & 2019)
Master TypeSpecifies if the Mailbox Database is part of a DAG/ Server.
DAG Name / ServerThe Database Accessibility Group (DAG) name. DAG allows you to replicate
your database where your mail is stored across any number of servers.
Database NameName of the mailbox database.
Mount StatusThe mount status of the mailbox stores on the server. Mailboxes contained in unmounted mailbox stores cannot receive incoming
messages.
Mailbox CountThe total number of mailboxes that reside in all mailbox stores and public folders.
Database Size (GB)The size of the mailbox database.
Available New Mailbox Space (GB)This represents the unallocated storage capacity within the mailbox database that's available for storing incoming emails. It's created when users delete emails or mailboxes, but the database hasn't reclaimed that space for future use.
Last Full BackupDetailed information about backups performed on storage groups on the connected server.
Circular Logging EnabledSpecifies whether or not circular logging is enabled. Circular Logging saves storage on your Exchange Server by preventing transaction logs from building up on the Server.
Days Since Last Full BackupIndicates the number of days passed since the last full backup operation was performed.
Database Statistics (2007)
Database NameName of the mailbox database
Mount StatusThe mount status of the mailbox stores on the server. Mailboxes contained in unmounted mailbox stores cannot receive incoming
messages.
Mailbox CountThe total number of mailboxes that reside in all mailbox stores and public folders.
Storage GroupThe exchange storage group name. A Storage Group is a grouping of one or more Mailbox Databases along with Log Files and a Checkpoint File. Not available for versions later than 2007.
Database Availability Groups
Database Availability Group NameThe name of the database availability group.
DAG MembersThe database availability group members.
DAG Members CountThe number of members in the particular database availability group.
Database Copy Statistics
Database NameThe name of the mailbox database.
Database StatusThe current status of the database. Possible Statuses are:
  • Failed - The mailbox database copy is in a Failed state because it is not suspended, and it is notable to copy or replay log files. While in a Failed state and not suspended, the system will periodically check whether the problem that caused the copy status to change to Failed has been resolved. After the system has detected that the problem is resolved, and barring no other issues, the copy status will automatically change to Healthy.
  • Seeding - The mailbox database copy is being seeded, the content index for the mailbox database copy is being seeded, or both are being seeded. Upon successful completion of seeding, the copy status should change to Initializing.
  • SeedingSource - The mailbox database copy is being used as a source for a database copy seeding operation.
  • Suspended - The mailbox database copy is in a Suspended state as a result of an administrator manually suspending the database copy by running the Suspend-MailboxDatabaseCopy cmdlet.
  • Healthy - The mailbox database copy is successfully copying and replaying log files, or it has successfully copied and replayed all available log files.
  • ServiceDown - The Microsoft Exchange Replication service is not available or running on the server that hosts the mailbox database copy.
  • Initializing - The mailbox database copy will be in an Initializing state when a database copy has been created, when the Microsoft Exchange Replication service is starting or has just been started, and during transitions from Suspended, ServiceDown, Failed, Seeding, SinglePageRestore, LostWrite, or Disconnected to another state. While in this state, the system is verifying that the database and log stream are in a consistent state. In most cases, the copy status will remain in the Initializing state for about 15 seconds, but in all cases, it should generally not be in this state for longer than 30 seconds.
  • Resynchronizing - The mailbox database copy and its log files are being compared with the active copy of the database to check for any divergence between the two copies. The copy status will remain in this state until any divergence is detected and resolved.
  • Mounted - The active copy is online and accepting client connections. Only the active copy of the mailbox database copy can have a copy status of Mounted.
  • Dismounted - The active copy is offline and not accepting client connections. Only the active copy of the mailbox database copy can have a copy status of Dismounted.
  • Mounting - The active copy is coming online and not yet accepting client connections. Only the active copy of the mailbox database copy can have a copy status of Mounting.
  • Dismounting - The active copy is going offline and terminating client connections. Only the active copy of the mailbox database copy can have a copy status of Dismounting.
  • DisconnectedAndHealthy - The mailbox database copy is no longer connected to the active database copy, and it was in the Healthy state when the loss of connection occurred. This state represents the database copy with respect to connectivity to its source database copy. It may be reported during DAG network failures between the source copy and the target database copy.
  • DisconnectedAndResynchronizing - The mailbox database copy is no longer connected to the active database copy, and it was in the Resynchronizing state when the loss of connection occurred. This state represents the database copy with respect to connectivity to its source database copy. It may be reported during DAG network failures between the source copy and the target database copy.
  • FailedAndSuspended - The Failed and Suspended states have been set simultaneously by the system because a failure was detected, and because resolution of the failure explicitly requires administrator intervention. An example is if the system detects unrecoverable divergence between the active mailbox database and a database copy. Unlike the Failed state, the system will not periodically check whether the problem has been resolved, and automatically recover. Instead, an administrator must intervene to resolve the underlying cause of the failure before the database copy can be transitioned to a healthy state.
  • SinglePageRestore - This state indicates that a single page restore operation is occurring on the mailbox database copy.
Based on these values, we want the Status attribute to be either Mounted (true for the server where the database is mounted) or Healthy (for the servers that hold a copy of it). For the ContentIndexState attribute, we want it to be always Healthy.
Copy Queue LengthThe Copy Queue Length shows the number of transaction log files waiting to be copied to the passive copy log file folder. A copy is not considered complete until it has been checked for corruption.
Content Index StateThe state of Microsoft Exchange Server content indexes:
  • Crawling - Database is in the process of indexing database content. Depending on the size of the database, this process could take some time to complete.
  • Disabled - Indexing for the database has been disable by an administrator.
  • Failed - An error has occurred causing the content index to fail.
  • FailedAndSuspended - The Failed and Suspended states have been set simultaneously by the system because a failure was detected, and because resolution of the failure explicitly requires administrator intervention.
  • Healthy - This indicates the Content Index is up to date and has not detected any issues. This is the only state in which a failover (automatic process) to a specific database copy can occur.
  • Seeding - A database copy is in the process of updating its Content Index from another database copy.
  • Suspended - The Suspended status occurs if an administrator manually pauses or suspends it from receiving updates from the active copy. This might be done to update a failed Content Index or to perform troubleshooting for other issues.
Latest Full Backup TimeLast full backup time for the mailbox database
Active CopyIf the database copy is active "True" is shown else,if Passive, "False" is shown
Days Since Latest Full BackupIndicates the number of days passed since the latest full backup operation was performed.

 

Client Access Server Role CountersExchange Server Version
Attribute nameDescription20072010201320162019
ASP.NET Counters
Application RestartsThe number of times the application has been restarted during the Web server's lifetime.
Worker Process RestartsThe number of times a worker process has restarted on the computer.
Request Wait TimeThe number of ms the most recent request was waiting in the queue.
ActiveSync Counters
ActiveSync Requests/secThe number of HTTP requests waiting to be assigned to a thread. (Average of 50-100.)
Pending Ping CommandsThe number of ping commands currently pending on the server. Ping Commands Pending are the number of hanging requests, which should be almost equal to the number of Direct Push and hanging sync users.
Pending Sync CommandsThe number of sync commands currently pending on the server. Sync Commands Pending are the number of hanging requests, which should be almost equal to the number of Direct Push and hanging sync users.
Requests QueuedThe number of HTTP requests queued in a thread.
Availability Service Counters
Availability Requests/secThe number of requests in the application request queue per second. The request can be only for free/busy information or include suggestions. One request may contain multiple mailboxes. Determines the rate at which Availability service requests are occurring.
Average Time to Process a Free Busy RequestThe average time to process a free/busy request in seconds. A single request may contain multiple mailboxes.
Current requestsThe number of HTTP requests waiting to be assigned to a thread.
Mailbox Session Hits/secThe number of hits in a mailbox session.
Public Folder Queries/secPublic Folder Queries per second is the number of mailboxes for which free busy information is requested from the public folders per second.
Public Folder Request Failures/secThe number of public folder free busy requests failed per second.
Outlook Web Access Counters
Current UsersThe number of users currently logged on to Outlook Web Access. This value monitors the number of unique active user sessions, so that users are only removed from this counter after they log off or their session times out. Determines current user load.
Outlook Requests/secThe number of Outlook requests processed each second. Determines current user load.
Average Search TimeThe average time elapsed while waiting for a search to complete.
Searches timed outThe number of Outlook requests timed out.
OWA Average Response TimeThe average time (in milliseconds) that elapsed between the beginning and end of an OEH or ASPX request. Used to determine the latency that a client is experiencing. The threshold value should be less than 100 ms at all times. Higher values may indicate high user load or higher than normal CPU time.
Autodiscover Counters
Discover Requests/secThe number of Autodiscover service requests processed each second. Determines current user load.
WebService Counters
Current ConnectionsThe current number of connections established with the Web service. Determines current user load.
Connection Attempts/secThe rate that connections to the Web service are being attempted. Determines current user load.
Current ISAPI Extension RequestsThe rate that Internet Server API (ISAPI) extension requests are received by the Web service. Determines current user load.
Other Request Methods/secThe rate HTTP requests are made that don't use the OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, MOVE, COPY, MKCOL, PROPFIND, PROPPATCH, SEARCH, LOCK, or UNLOCK methods. Determines current user load.
Requests/secThe number of requests processed each second. Determines current user load.
Completed requests/secThe number of requests completed each second. Determines current user load.
RPC Client Access Counters
Client RPC Average LatencyThe average latency, in milliseconds, of RPC requests made to the Exchange Information Store over the last 1024 packets.
RPC Operations/secThe rate at which RPC operations are being processed by the Exchange Information Store per second.
IS RPC RequestsThe current number of RPC requests simultaneously active in the Exchange Information Store at a given point in time.
User CountThe number of users currently connected to the Exchange RPC Client Access service at a given point in time.
Exchange Control Panel Counters
Outbound Proxy Requests - Average Response TimeThe average time (in ms) that requests sent to a secondary Client Access server took to complete during the sampling period. The threshold value should be under 6,000 ms.
Requests - Average Response TimeThe average time (in ms) the Exchange Control Panel took to respond to a request during the sampling period. The threshold value should be under 6,000 ms.
ASP.net Request Failures/secThe number of failures per second detected by ASP.NET in the Exchange Control Panel.
Powershell Runspaces - Average Active TimeThe average time (in seconds) that a Windows PowerShell runspace stays active while executing cmdlets in the Exchange Control Panel during the sampling period.
Powershell Runspaces/secThe number of Windows PowerShell runspaces created per second in the Exchange Control Panel.
RBAC sessions/secThe number of RBAC sessions loaded per second in the Exchange Control Panel.
Unified Messaging Counters
Percent of failed mailbox connection attempts over the last hourThe percentage of mailbox connection attempts that failed in the last hour. The threshold value should be less than 5%.
Percent of inbound calls rejected by the UM service over the last hour.The percentage of inbound calls that were rejected by the Microsoft Exchange Unified Messaging service over the last hour
Percent of inbound calls rejected by the UM worker process over the last hourThe percentage of inbound calls that were rejected by the Unified Messaging worker process over the last hour.
Percent of messages successfully processed over the last hourThe percentage of messages that were successfully processed by the Microsoft Exchange Unified Messaging service over the last hour.
Percent of partner voice message transcription failures over the last hourThe percentage of voice messages for which transcription failed in the last hour.
Calls disconnected on irrecoverable internal errorThe number of calls disconnected after an internal system error occurred.
Calls disconnected by user failureThe total number of calls disconnected after too many user entry failures.
Current callsThe number of calls that are currently connected to the UM server.
Total calls per secondThe number of new calls that have arrived in the last second.
User Response LatencyThe average response time, in milliseconds, for the system to respond to a user request. This average is calculated over the last 25 calls. This counter is limited to calls that require significant processing.
CAS OAB Download Counters
Download Task QueuedThe number of OAB download tasks queued since the File Distribution service started. The threshold value should be 0 at all times.
Download Tasks CompletedThe number of OAB download tasks completed since the File Distribution service started. The default value is every 480 minutes or 8 hours. The threshold value should be less than or equal to 3 per day.

 

Hub/Edge Transport Role CountersExchange Server Version
Attribute nameDescription20072010201320162019
Transport Database Counters (HUB,EDGE)
IO Log Writes/secThe rate of log file write operations completed. Determines the current load.
IO Log Reads/secThe rate of log file read operations completed. Determines the current load.
Log Generation Checkpoint DepthThe amount of work (in count of log files) that needs to be redone or undone to the database files if the process fails.
Version Buckets AllocatedTotal number of version buckets allocated. Shows the default backpressure values as listed in the edgetransport.exe.config file.
IO Database Reads/secThe rate of database read operations completed. Determines the current load.
IO Database Writes/secThe rate of database write operations completed. Determines the current load.
Log Record Stalls/secThe number of log records that can't be added to the log buffers per second because they are full. If this counter is nonzero most of the time, the log buffer size may be a bottleneck.
Log Threads WaitingThe number of threads waiting for their data to be written to the log to complete an update of the database. If this number is too high, the log may be a bottleneck.
Transport Dumpster Counters (HUB,EDGE)
Dumpster SizeThe total size (in bytes) of mail items currently in the transport dumpster on this server.
Dumpster Inserts/secThe rate at which items are inserted into the transport dumpster on this server. Determines the current rate of transport dumpster inserts.
Dumpster Item CountThe total number of mail items currently in the transport dumpster on this server. Shows the current number of items being held in the transport dumpster.
Dumpster Deletes/secThe rate at which items are deleted from the transport dumpster on this server. Determines the current rate of transport dumpster deletions.
Transport Queue Length Counters (HUB,EDGE)
Aggregate Delivery Queue Length All QueuesThe number of messages queued for delivery in all queues. The threshold should be less than 3,000 and not more than 5,000.
Active Remote Delivery Queue LengthThe number of messages in the active remote delivery queues. The threshold should be less than 250.
Active Mailbox Delivery Queue LengthThe number of messages in the active mailbox queues. The threshold should be less than 250.
Submission Queue LengthThe number of messages in the submission queue. The threshold should be less than 100. If sustained high values occur, investigate Active Directory and Mailbox servers for bottlenecks or performance-related issues.
Active Non-SMTP Delivery Queue LengthThe number of messages in the drop directory used by a Foreign connector. The threshold should be less than 250.
Retry Mailbox Delivery Queue LengthThe number of messages in a retry state attempting to deliver a message to a remote mailbox. The threshold should be less than 100.
Retry Non-SMTP Delivery Queue LengthThe number of messages in a retry state in the non-SMTP gateway delivery queues. The threshold should be less than 100.
Retry Remote Delivery Queue LengthThe number of messages in a retry state in the remote delivery queues. The threshold should be less than 100.
Unreachable Queue LengthThe number of messages in the Unreachable queue. The threshold should be less than 100.
Largest Delivery Queue LengthThe number of messages in the largest delivery queues. The threshold value should be less than 200 for the Edge Transport and Hub Transport server roles.
Poison Queue LengthThe number of messages in the poison message queue. The threshold value should be 0 at all times.
Transport Load Assessment Counters (HUB,EDGE)
Messages Submitted/secThe number of messages queued in the Submission queue per second. Determines current load. Compare values to historical baselines.
Messages Completed Delivery/secThe number of messages delivered per second. Determines current load. Compare values to historical baselines.
Inbound Local Delivery Calls/secThe number of local delivery attempts per second. Determines current load. Compare values to historical baselines.
Average Bytes Per MessageThe average number of message bytes per inbound message received. Determines sizes of messages being received for an SMTP receive connector.
Messages Received/secThe number of messages received by the SMTP server each second. Determines current load. Compare values to historical baselines.
Messages Sent/secThe number of messages sent by the SMTP send connector each second. Determines current load.
Items Queued for Delivery/secThe number of messages queued for delivery per second. Determines current load.
Inbound Message Delivery Attempts/secThe number of attempts for delivering transport mail items per second. Determines current load. Compare values to historical baselines.
Messages Queued for Delivery/secThe number of messages queued for delivery per second. Determines current load. Compare values to historical baselines.
Edge Sync Counters(EDGE)
Total topology updatesExchange topology updates found by EdgeSync
Exchange servers totalTotal number of Exchange Servers found by EdgeSync.
Edge servers totalTotal number of Edge Transport servers found by EdgeSync.
Hub transport servers totalTotal number of Hub Transport servers found by EdgeSync.
Edge servers leased totalTotal number of Edge Transport servers leased by EdgeSync.
Edge objects added/secThe rate of Edge objects added per second by EdgeSync.
Edge objects deleted/secThe rate of Edge objects deleted per second by EdgeSync.
Edge objects updated/secThe rate of Edge objects updated per second by EdgeSync.
Scan jobs completed successfully totalThe total number of scan jobs completed successfully by EdgeSync.
Scan jobs failed because could not extend lock totalThe total number of EdgeSync scan jobs that failed because EdgeSync could not extend its lease of an Edge Transport server.
Scan jobs failed because of directory error totalThe total number of EdgeSync directory errors.
Scan jobs failed because could not lock totalThe total number of Scan jobs failed because could not lock total.
Source objects scanned/secThe rate of Active Directory objects scanned per second by EdgeSync.
Target objects scanned/secThe rate of Edge objects scanned per second by EdgeSync.
Recipient Filter Agent Counters(EDGE)
Recipients rejected by recipient validation/secShow the number of recipients rejected by recipient validation per second.
Recipients rejected by block list/secShow the number of recipients rejected by block list per second.
Sender Filter Agent Counters(EDGE)
Messages filtered by sender filter/secShow the number of messages filtered by the Sender Filter agent per second.
DNS queries/secThe number of DNS queries per second performed by the Sender Id agent.
Attachment Filtering Counters(EDGE)
Messages attachment filteredThe number of messages that were blocked, stripped of attachments, or silently deleted (as per configuration) by the attachment filtering agent.
Messages filtered/secThe number of messages per second that the attachment filtering agent blocked, stripped of attachments, or silently deleted. If this rate rises greatly beyond what is “normal” for the Exchange server, it may indicate that the organization is being flooded with malicious e-mail.
Content Filter Agent Counters(EDGE)
Messages deletedThe total number of messages that were deleted by Content Filter Agent.
Messages quarantinedThe total number of messages that were quarantined by Content Filter Agent.
Messages rejectedThe total number of messages that were rejected by Content Filter Agent.
Messages that bypassed scanningThe total number of messages that bypass scanning.
Messages scanned/secThe number of messages scanned per second.
Active Directory Application Mode (ADAM) Counters (EDGE)
LDAP Searches/secThe number of Lightweight Directory Access Protocol (LDAP) search requests issued per second. Used to determine the current LDAP search rate.
LDAP Writes/secThe rate at which LDAP clients perform write operations.

 

Edge Transport Role CountersExchange Server Version
Attribute nameDescription20072010201320162019
Exchange-Agents
Agent NameThe Name of the agent counters.
Average Agent Processing Time in secThe average agent processing time in seconds per event. The threshold value should be less than 20
Total Agent InvocationsThe total number of invocations since the last restart. The current invocation rate.
Message Hygiene Counters
Average Scan TimeAverage time taken to perform scanning of mailboxes as part of the message hygiene using scheduled and on-demand scans. A high value could indicate a bottleneck in scanning.
Scan Requests Rejected/secThe number of scan requests in this application pool’s queue that were rejected.
Scan Requests Being ScannedThe number of scan processes currently running.
Scan Requests Processing Time Per RequestThe amount of time spent in processing a request.
Antimalware Processing Time Per RequestThe amount of time taken for the Antimalware engine to process an item.
Unhealthy Antimalware enginesAntimalware engines with errors in engine functioning.
Scan Requests Fatal ErrorsIndicates what percentage of scan requests submitted encountered errors that prevented the processing of those scan requests.
Scan Request TimeoutsThe number of scan requests that timed out in the last minute.
Scan Processes RunningThe number of scan processes currently running.
Scan Time Per RequestThe scan time per request.
Scan Requests Processed/secThe number of scan requests processed per second.
Scan Request Wait Time Per RequestThe time for which a scan request waits in the internal queue.
Scan Requests QueuedThe number of scan requests that are currently in the internal queue.
Scan Requests Submitted/secThe number of scan requests submitted per second, including requests accepted and rejected by the scanning system.
SafetyNet Counters
Resubmission LatencyAverage time spent to resubmit each message when processing a Safety Net resubmit request.
SafetyNet Resubmission RateThe number of messages resubmitted from Safety Net. Resubmit requests are generally triggered by HA but can also be requested manually via New-ResubmitRequest.
SafetyNet Resubmit Request rateNumber of resubmit requests that were made to safety net during the sampling period.
Shadow SafetyNet Resubmission RateTotal number of messages resubmitted from Shadow Safety Net. Shadow resubmit requests occur when a primary Safety Net server cannot be reached for several hours.
Shadow SafetyNet Resubmit Request rateNumber of shadow resubmit requests that were made to shadow safety net during the sampling period.
Resubmit Request rateTotal number of resubmit requests encountered per resubmit request state.

 

Unified Messaging Server Role CountersExchange Server Version
Attribute nameDescription20072010
Unified Messaging Counters
Percentage of failed mailbox connection attempts over the last hourThe percentage of mailbox connection attempts that failed in the last hour.
Percentage of inbound calls rejected by the um service over the last hourThe percentage of inbound calls that were rejected by the Microsoft Exchange Unified Messaging service over the last hour.
Percentage of inbound calls rejected by the um worker process over the last hourThe percentage of inbound calls that were rejected by the UM worker process over the last hour.
Percentage of messages successfully processed over the last hourThe percentage of messages that were successfully processed by the Microsoft Exchange Unified Messaging service over the last hour.
Percentage of partner voice message transcription failures over the last hourThe percentage of voice messages for which transcription failed in the last hour.
Directory access failuresThe number of times that attempts to access Active Directory failed.
Calls disconnected on irrecoverable internal errorThe number of calls disconnected after an internal system error occurred.
Operations over six secondsThe number of all UM operations that took more than six seconds to complete. This is the time during which a caller was waiting for UM to respond.
Calls disconnected by callers during um audio hourglassThe number of calls during which the caller disconnected while Unified Messaging was playing the audio hourglass tones.
Total inbound calls rejected by the um serviceThe total number of inbound calls that were rejected by the Microsoft Exchange Unified Messaging Service since the service was started.
Total inbound calls rejected by the um worker processThe total number of inbound calls that were rejected by the UM Worker process since the service was started.
Call answer queued messagesThe number of messages created and not yet submitted for delivery.
Direct access failuresThe number of times that attempts to access Active Directory failed.
Hub transport access failuresThe number of times that attempts to access a Hub Transport server failed. This number is only incremented if all Hub Transport servers were unavailable.
Unhandled exceptions/secThe number of calls that were disconnected after an internal system error occurred in the last second.
Queued ocs user event notificationsThe number of notifications that have been created and not yet submitted for delivery. Represents the number of missed call notifications that have been generated in the Office Communications Server environment and have not been submitted for delivery.
Mailbox server access failuresThe number of times the system did not access a Mailbox server.

 

Overview - Common CountersExchange Server Version
Attribute nameDescription20072010201320162019
Server Component States
Component NameSpecifies the Exchange Component name.
StateSpecifies the Exchange Component Status.
Exchange Services
Service NameSpecifies the Exchange Agent Service name.
StatusSpecifies the Exchange Agent Service Status.
AvailabilitySpecifies the availability of the Exchange Agent Service.
AD Access Domain Controllers
Domain ControllerThe specified domain controller
LDAP Read TimeThe time in milliseconds that a LDAP read request takes to be fulfilled. The average value should be under 50 milliseconds. Maximum values should not exceed 100 milliseconds.
LDAP Search TimeThe time in milliseconds that it takes a Lightweight Directory Access Protocol (LDAP) search request to be fulfilled. The threshold values should be below 50 ms. Maximum values should not be higher than 100 ms.
LDAP searches timed-out per MinuteThe number of LDAP searches that returned LDAP_Timeout during the last minute. The threshold value should be below 10 at all times for all roles. Higher values may indicate issues with Active Directory resources.
Long-running LDAP operations Per MinuteThe number of LDAP operations on this domain controller that took longer than the specified threshold per minute. The default threshold value is 15 seconds. The threshold values should be below 50 ms. Higher values may indicate issues with Active Directory resources.

 

Host Performance CountersExchange Server Version
Attribute nameDescription20072010201320162019
Disk Utilization
Free Disk SpaceThe percentage of free space on the disk (in %).
Average Disk Reads/secNumber of disk reads per second on the physical disk. This counter should be well under the maximum capacity for the disk device.
Average Disk Writes/secNumber of disk writes per second on the physical disk. This counter should be well under the maximum capacity for the disk device.
Memory Utilization
Memory UsedThe memory space used by the server (in GB).
Free Physical MemoryThe amount of free physical memory available (in %).
% Memory UsedThe percentage of memory space used by the server (in %).
Total MemoryTotal amount of physical memory available to the operating system (in GB).
Exchange Domain Controllers Connectivity Counters
Cache Hits/secThe number of object found in cache events per second.
Cache Misses/secThe number of objects not found in cache events per second.
LDAP Searches/secThe number of LDAP search requests issued by a process per second.
Outstanding Asyncronous ReadsThe number of outstanding LDAP read requests.
Memory Pages
Pages Input/secThe rate at which pages are read from disk to resolve hard page faults.
Pages Output/secThe rate at which pages are written to disk to free up space in physical memory. A high rate of pages output might indicate a memory shortage.
Total Pages/secThe rate at which pages are read from or written to disk to resolve hard page faults. This counter is a primary indicator of the kinds of faults that cause system-wide delays.
Page Reads/secThe number of read operations, without regard to the number of pages retrieved in each operation.
Page Writes/secThe number of write operations, without regard to the number of pages written in each operation.
Transition Pages Repurposed/secThe rate at which the number of transition cache pages were reused for a different purpose.

 

Note: The metrics under the Exchange Queues section are mapped under Settings → Performance Polling → Optimize Data Collection.

QueuesExchange Server Version
Attribute nameDescription20072010201320162019
Exchange Queues
Queue NameThe identity of the queue in the form of <Server>\ <Queue>. Learn more
StatusThe current queue status. A queue can have one of the following status values: Active, Connecting, Suspended, Ready, or Retry. Learn more
Message CountThe number of messages in the queue.
VelocityThe drain rate of the queue, calculated by subtracting the value of Incoming Rate from the value of Outgoing Rate. Learn more
Delivery TypeRepresents how the Transport service intends to transmit the message to the next hop, which could be the ultimate destination of the message, or an intermediate hop along the way. The value External indicates the next hop for the queue is outside the Exchange organization. The value Internal indicates the next hop for the queue is inside the Exchange organization. Possible values: Internal, External, Undefined
Next Hop DomainThe next domain where the messages hops from the current queue. For delivery queues, the value of this field is effectively the name of the queue. The value of NextHopDomain isn't always a domain name. For example, the value could be the name of the target Active Directory site or database availability group (DAG).
Exchange 2003 Performance Counters
Attribute nameDescription
SMTP Connections
Inbound ConnectionsThe total number of connections that were currently inbound.
Outbound ConnectionsThe number of connections that were currently outbound.
SMTP statistics
Local Retry Queue LengthThe number of messages in the local retry queue.
Remote Retry Queue LengthThe number of messages that were in the retry queue for remote delivery.
Remote Queue LengthThe number of messages that were in the remote queue.
Messages Pending RoutingThe number of messages that were categorized but not routed.
Messages in Local DeliveryThe number of messages that were currently being processed by a server event sink for local delivery.
Currently Undeliverable MessagesThe number of messages that were reported as currently undeliverable by routing.
Categorizer Queue LengthThe number of messages in the categorizer queue waiting to be categorized.
POP & IMAP Connections
Current POP ConnectionsThe total number of POP connections opened since the computer was last started.
Current IMAP ConnectionsThe total number of IMAP connections opened since the computer was last started.
Information Store Mailbox statistics
Receive Queue SizeThe number of messages in the mailbox's receive queue. The threshold value should be below 500 at all times.
Send Queue SizeThe number of messages in themailbox's send queue. In a server with no mail-enabled mailbox, it should be below 10. Otherwise, it should be below 500 at all times.
Active Client LogonsThe active client logons to Mailbox Stores during the specified time period.
Client LogonsThe client logons to Mailbox stores during the specified time period.
Logon Operations Per MinThe number of logon operations to Mailbox stores per minute.
Message Recipients Delivered Per minThe message delivery rate. System Monitor data should match the Exchange Load Generator predicted value for message received rate.
Messages Delivered Per minThe message submission rate.
Messages Sent Per minThe message sent rate.
Mailbox Used SpaceThe amount of space used by the Mailbox.
Information Store Public Folder statistics
Send Queue SizeThe number of messag es in the public store's send queue.
Receive Queue SizeThe number of messag es in the public store's receive queue.
Active Client LogonsThe active client logons to Public Folder Stores during the specified time period.
Client LogonsThe client logons to Public Folder Stores during the specified time period.
Logon Operations Per MinThe number of logon operations to Public Folders per minute.
Messages Delivered Per minThe message delivery rate.
Message Recipients Delivered Per minThe message recipients delivery rate. System Monitor data should match the Exchange Load Generator predicted value for message received rate.
Messages Sent Per minuteThe message sent rate.
Messages Submitted Per minuteThe message submission rate.
Public Folders Used SpaceThe amount of space used by Public Folders.
Information Store Connections & Users
Information Store Active Connection CountThe number of connections that have shown some activity in the last 10 minutes.
Information Store Connection CountThe number of client processes connected to the information store.
Information Store Active User CountThe number of user connectio ns that have shown some activity in the last 10 minutes.
MTA statistics
MTA Work Queue LengthThe number of messages in the MTA work queue. This indicates the number of messages not yet processed to completion by the MTA.
MTA Message Bytes Per MinThe rate at which message bytes are processed.
MTA TCP/IP Received Bytes Per MinThe rate at which bytes are received over a TCP/IP connection.
MTA TCP/IP Transmit Bytes Per MinThe rate at which bytes are transmitted over a TCP/IP connection.
MTA Total Recipients QueuedThe maximum number of recipients permitted in the MTA queues.
MTA Work Queue BytesThe total volume of messages (in MB) stored in the message transfer agent (MTA).
Information Store statistics
Current Pending Local DeliveryMessages currently pending in the MTA Queue
Current message from MSExchangeMTAMessages currently in transit from MSExchangeMTA to Exchange Store
Currentmessages to MSExchangeMTAMessages currently in transit to MSExchangeMTA from Exchange Store
Messages Received Per MinThe number of messages received by the SMTP server each min
Messages Sent Per MinThe number of messages sent by the SMTP server each min
HSOT Cache HitsThe number of objects found in cache events per second.
Directory & Event Service statistics
Pending Replication SynchronizationsThe number of directory synchronizations that are queued for this server. This counter helps identify replication backlogs - the higher the number, the larger the backlog.
Remaining Replication UpdatesThe number of directory synchronizations remaining. This counter helps identify replication backlogs - the higher the number, the larger the backlog.
Notify QueueThe queue of store notifications waiting to be processed.
Address Lists Queue LengthThe number of entries in the Address List queue.
Message Transfer Agent Connections
MTA Queue LengthThe number of outstanding messages queued for transfer
MTA Queued BytesThe total volume of message content (in MB) that is stored in the queue of the Message Transfer Agent.
MTA Current Inbound AssociationsThe number of inbound (remotely initiated) associations between the MTA and the connected MTA. MTAs can open multiple associations, if additional transfer throughput is necessary.
MTA Current Outbound AssociationsThe number of inbound (locally initiated) associations between the MTA and the connected MTA. MTAs can open multiple associations, if additional transfer throughput is necessary.

Loved by customers all over the world

"Standout Tool With Extensive Monitoring Capabilities"

It allows us to track crucial metrics such as response times, resource utilization, error rates, and transaction performance. The real-time monitoring alerts promptly notify us of any issues or anomalies, enabling us to take immediate action.

Reviewer Role: Research and Development

carlos-rivero
"I like Applications Manager because it helps us to detect issues present in our servers and SQL databases."
Carlos Rivero

Tech Support Manager, Lexmark

Trusted by over 6000+ businesses globally