- About LogicMonitor
- Cloud Monitoring
- Dashboards and Widgets
- Getting Started
- LM Service Insight
- Backup and Recovery Systems
- Cloud Resources
- Networking & Firewalls
- Cisco VoIP Monitoring
- Cisco UCS Monitoring
- Brocade Application Delivery Controllers
- Checkpoint Firewalls
- Cisco APIC Monitoring
- Cisco ASA/ASR
- Cisco Device SNMP and NTP Configuration
- Cisco Firepower Chassis Manager Monitoring
- Cisco IP SLA Monitoring
- Citrix NetScalers
- Dell Switch Monitoring
- F5 BIG-IP Monitoring
- Fortinet Fortigate Firewalls
- Infoblox Monitoring
- Interface Status alerting and Bandwidth Utilization
- Juniper SRX
- Kemp LoadMaster Load Balancers
- Meraki Cloud Access Controllers
- NetFlow Monitoring
- Palo Alto Firewalls
- pfSense Firewalls
- Sonicwall Firewalls
- Operating Systems & Virtualization
- VMware Horizon Monitoring
- Citrix XenServer Monitoring
- Citrix XenApp/XenDesktop Monitoring
- ESXi Servers and vCenter/vSphere Monitoring
- Linux Disk Performance
- Linux File Systems reporting more than 100% usage
- Linux Inodes
- Linux Interface Bandwidth Utilization
- Linux NFS Server
- Monitoring a Domain Controller (DC)
- Monitoring Remote Linux Files
- NTP Configuration
- NTP Monitoring
- Nutanix HyperConverged Infrastructure
- SNMP v1/v2 Configuration
- SNMPv3 Configuration
- Solaris Monitoring
- Troubleshooting Perfmon Access
- Troubleshooting SNMP
- Troubleshooting WMI
- VMware vCenter Server Appliance (VCSA) Monitoring
- Windows Cluster Monitoring
- Windows Firewall Issues
- Windows Server 2000
- Windows XP
- Applications & Databases
- Microsoft Office 365 Monitoring
- OpenMetrics Monitoring
- Zoom Monitoring
- Apache Monitoring
- Cassandra Monitoring
- ConnectWise Monitoring
- Email Service Monitoring
- Java Applications
- Lighttpd Monitoring
- Microsoft Exchange Monitoring
- Microsoft SQL Server Monitoring
- MongoDB Monitoring
- MySQL Monitoring
- Nginx Monitoring
- Oracle Monitoring
- Pick & D3
- Postfix Monitoring
- PostgreSQL Monitoring
- RabbitMQ Monitoring
- Redis Monitoring
- Twilio Monitoring
- Varnish HTTP Accelerator
- Server & Operations Hardware
- Storage Systems
- Cisco HyperFlex Monitoring
- Apache Hadoop Monitoring
- EMC ECS
- EMC Isilon Monitoring
- EMC Unity Monitoring
- EMC VMAX
- EMC VNX/Clariion SAN
- EMC VNXe
- EMC VPLEX
- EMC XtremIO
- HPE 3PAR Storage
- HP MSA / StorageWorks / P2000
- HP P4000/Lefthand SANs
- NetApp E/EF-Series Monitoring
- NetApp Monitoring
- Nimble Storage
- Panzura Cloud Storage
- Quantum Small Tape Libraries
- VMware vSAN Monitoring
- Rest API Developers Guide
- RPC API Developers Guide - Deprecated
- Servicenow CMDB Integration
- Terminology and Syntax
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:
- 2007+ – DataSource names appended with “2007+” apply to Exchange versions 2007, 2010 and 2013 (e.g. Microsoft_Exchange_Replication_2007+)
- 2016+ – DataSource names appended with “2016+” apply to Exchange versions 2016 and 2019 (e.g. Microsoft_Exchange_Replication_2016+)
Note: There are two DataSources that require no compatibility versioning: “WinExchange Processes” and “WinExchangeServices”.
Considerations: Migration from WinExchange* DataSources
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:
- WMI – Used by DataSources compatible with Exchange versions 2016 and 2019
- Perfmon – Used by DataSources compatible with versions 2007, 2010 and 2013
Ensure that the appropriate access method (WMI or Perfmon) is enabled on the host.
Common steps for troubleshooting issues with Microsoft Exchange monitoring include:
- Ensure WMI (or Perfmon for Exchange versions 2013 or earlier) is correctly configured on the host.
- Ensure that the system.categories property for the host (as stored in LogicMonitor) is assigned the appropriate system category tag (i.e. MicrosoftExchange2007, MicrosoftExchange2010, MicrosoftExchange2013, MicrosoftExchange2016 or MicrosoftExchange2019).
- If the system.categories property is not set correctly, check that the addCategory_MicrosoftExchange PropertySource is imported.
- Open the addCategory_MicrosoftExchange PropertySource and run the Test AppliesTo and Test Script functions to check for execution errors.
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:
- Less reliance on AppliesTo scripting. Legacy DataSources rely heavily on the AppliesTo function of “isWindows()”. While once sufficient, the broadness of this function now creates incompatibility issues.
- Better version compatibility. Beginning with Exchange 2016, Microsoft made deprecations and other changes to its performance counters. New DataSources were needed to account for these changes so that accurate data collection is maintained.
- Improved Performance. The new DataSources take advantage of WMI for data collection for Exchange 2016 and 2019. This brings a big performance improvement over Perfmon queries, which were blanketly used previously and could result in high CPU usage, long execution times, and even timeouts. Additionally, all DataSources now leverage BatchScript which greatly improves execution time and resource usage.
- Future Proofing. The new DataSources are more modularized and version aware. This provides more control over compatibility and eliminates the need for backward compatibility across all Exchange versions (current and future).
LogicModules in Microsoft Exchange Package
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.
In this Article: