Time to upgrade! NAM is scheduled for end of support. It's time to move to Dynatrace our all-in-one software intelligence platform.

Front-end monitoring - MS Exchange

In the MS Exchange section you set parameters for the Exchange analyzer, that is, regular expressions for user identification, detection of operation sequences and availability reporting options and others.


The main task for the NAM Probe in Microsoft Exchange Server monitoring is to provide measurements of efficiency of the MS-RPC/ROEP network protocol. NAM Probe also analyzes operations for which the users authenticate themselves in an Exchange server.

The MS Exchange analyzer is used to detect and monitor Microsoft Exchange RPC-based operations and return metrics on user actions. In addition, the NAM Probe gathers information on Microsoft Exchange operations and errors (a general distinction is made between server and protocol error types). To activate Exchange monitoring, create a dedicated user-defined software service.


To view information about MS Exchange failures in DMI reports, access the Availability tab and configure the appearance of a specific failure type in a DMI report.

You can configure MS Exchange availability globally or at the software services

For global configuration, open the NAM Probe configuration and go to Global ► Front-End Monitoring ► MS Exchange ► Availability. For the software service level, select the Availability tab in the Edit Rule window.

The following failure types are provided from which you can choose to enable or disable their appearance.

Transport failures

No response

Incomplete response. Incomplete response. A hit with no response from a server. Disabled by default.

Aborted response

Incomplete response. A response aborted by the user. Enabled by default.

HTTP errors

The NAM Probe is able to deliver information on seven HTTP error groups (“categories”).

  • HTTP client errors (4xx)
  • HTTP server errors (5xx)
  • HTTP unauthorized errors
  • HTTP Not Found errors
  • HTTP client errors (category 3)
  • HTTP server errors (category 1)
  • HTTP server errors (category 2)

You can decide whether each of these should be taken into account when calculating (failures transport). Note that HTTP client errors (4xx), HTTP server errors (5xx), HTTP unauthorized errors, HTTP Not Found errors, and HTTP server errors (category 1) have configurable contents. For more information, see Web - Errors.

For more information