Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
The Microsoft Exchange package consists of a set of LogicModules that provides comprehensive out-of-the-box monitoring for the Microsoft Exchange mail and calendaring server.
Note: LogicMonitor also offers monitoring for online Exchange via its Microsoft Office 365 integration package. See Microsoft Office 365 Monitoring for more information.
As of the v.125 release of the LogicMonitor platform (September 2019), the Microsoft Exchange package is compatible with versions 2007 through 2019. As Microsoft releases newer versions of Exchange, LogicMonitor will test and extend coverage as necessary.
For the majority of DataSources that make up this package, there are two versions of each DataSource: one version that is compatible with Exchange versions 2007, 2010, and 2013; and one version that is compatible with Exchange versions 2016 and 2019. These versions are necessary to account for deprecations and other changes that Microsoft made to its performance counters in Exchange 2016.
The DataSource names in this package are appended with Exchange version information to delineate which set of versions a particular DataSource applies to:
Note: There are two DataSources that require no compatibility versioning: “WinExchange Processes” and “WinExchangeServices”.
In September of 2019, LogicMonitor released a new set of Microsoft Exchange DataSources. If you are currently monitoring Microsoft Exchange using the legacy WinExchange* DataSources, you will not experience any data loss upon importing the newer DataSources in this package. This is because DataSource names have been changed to eliminate module overwriting.
However, you will collect duplicate data and receive duplicate alerts for as long as both sets of DataSources are active. For this reason, we recommend that you disable the legacy WinExchange* DataSources. When a DataSource is disabled, it stops querying the host and generating alerts, but maintains all historical data. At some point in time, you may want to delete the legacy DataSources altogether, but consider this move carefully as all historical data will be lost upon deletion. For more information on disabling DataSources, see Disabling Monitoring for a DataSource or Instance.
Important: There are two legacy WinExchange DataSources that have been allowed to remain with the new set of DataSources (i.e. they have not been replaced): “WinExchange Processes” and “WinExchangeServices”. These should NOT be disabled. Both are universal across all Exchange versions and will continue working seamlessly.
The DataSources in this package rely on WMI or Perfmon to collect data from your Microsoft Exchange system:
Ensure that the appropriate access method (WMI or Perfmon) is enabled on the host.
Common steps for troubleshooting issues with Microsoft Exchange monitoring include:
Q: Why did LogicMonitor perform such an extensive overhaul of the now-legacy Microsoft Exchange (i.e. WinExchange*) DataSources?
A: The original Microsoft Exchange DataSources were developed and released many years ago. Maturity in the Exchange product (and LogicMonitor platform) have since given us many compelling reasons to restructure our Microsoft Exchange package. These reasons include:
LogicMonitor’s out-of-the-box monitoring package for Microsoft Exchange contains the following LogicModules. Please ensure that all of these LogicModules are imported into your LogicMonitor platform.
When setting static datapoint thresholds on the various metrics tracked by this integration package, LogicMonitor follows the technology owner’s best practice KPI recommendations. If necessary, we encourage you to adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Tuning Static Thresholds for Datapoints.
In This Article