We are excited to announce that the Exchange team has released the Exchange 2013 Management Pack. You can find the Management Pack here and the guide here. The guide walks through the details of deploying, configuring and using the Management Pack.
In this blog, I am focusing on describing the benefits of the Management Pack, as well as some of the internals of how it works, and how it is different from previous Exchange Management Packs.
My target audience for the blog post is the Operations Manager administrator.
The Exchange team takes monitoring seriously, and they have created a pretty comprehensive Management Pack in terms of monitoring coverage, with the primary focus being MTTR, i.e. reduced downtime for your Exchange environment.
The Management Pack contains about 75 monitors that cover Exchange component health (such as Hub Transport health), customer touch point health (such as “is OWA working”), clustered scenarios, as well as dependencies monitoring (“is Active Directory healthy”). Monitoring covers primarily availability and performance scenarios.
With this Management Pack, the Exchange team is sharing knowledge and experience from managing the Office 365 environment, with its extreme demands on availability and performance. This means a lot has been done for you already, i.e. the relevance of alerts is high. Basically Exchange developers get notified 24x7 on this same set of monitors, and (similar to you) they are not interested in being awakened in the middle of the night for some irrelevant or non-actionable alerts.
The Exchange team is also sharing knowledge online for the monitors, so each monitor has a link to online knowledge.
The Exchange 2013 product comes with monitoring “built in”, more on that below. This means that Exchange itself has means to detect and try to automatically recover from availability and performance issues, before an operator is notified. This means reduced alert noise, as well as reduced administrative overhead for the Exchange product itself. In concrete terms, an Exchange server may detect an issue, then try for some time to fix it automatically. Only after the automatic recovery attempts have failed is the operator notified via an alert.
The Management Pack is very simple. It contains a handful of classes, 3 views, and about 75 monitors described here. There are also some dependency monitors.
All the monitors are simple event-based monitors using events in the Microsoft-Exchange-ManagedAvailability/Monitoring event log, logged by each Exchange server. So, each Exchange server is responsible for monitoring itself and its health.
In terms of scalability, this means this Management Pack will have a low impact to your Operations Manager environment. You will not require a separate Management Group for this MP for scalability purposes.
If you look at the Management Pack in some tool like MP Viewer, as I am sure some of you will, you will discover that there are not 75 monitors in the Management Pack. This is because the Management Pack has logic to dynamically determine the set of monitors by communicating with the built-in monitoring features of Exchange. More on that below. The way to see the monitors is by installing the Management Pack in an Operations Manager environment with monitored Exchange servers and using Health Explorer (you can also see them listed in the Management Pack Guide).
If you are familiar with the Exchange 2010 Management Pack, you know that it had a service called the correlation engine that ran on the Root Management Server. It basically correlated health data from all monitored Exchange components. In the Exchange 2013 Management Pack, the correlation engine is no longer used. Each monitored Exchange server is responsible for monitoring its own health, and simply reports this via the Operations Manager agent. There is a little bit of roll-up going on, from Exchange server to Organization health. There are no special components running on the Operations Manager Management Servers.
The Exchange 2010 Management Pack had tens of classes, leading to a pretty complex health model and many object instances being created. The Exchange 2013 Management Pack is very simple. It has only a few classes and should have a very low impact on Operations Manager in terms of instance space.
There are no performance counters collected by this Management Pack (as mentioned above, the monitoring does cover performance scenarios). However, all Exchange PerfMon counters are still available. It should be simple to create your own performance collection rules, if you do require them.
This means that by default there is way less pressure on the Management Group compared to the Exchange 2010 Management Pack, since there are no performance counters to store. But, what about reporting? There are also no reports in this Management Pack. The primary focus of this version of the Management Pack is reduced MTTR. However, you can use some of the built-in Operations Manager reports (such as the Health report) to track organization availability, or define SLAs against the Organization. Exchange is also looking for your feedback on this topic, feel free to comment on this post and I will pass that information along.
Exchange 2013 has a built in monitoring engine called Managed Availability. It runs on every Exchange server. It contains logic for how to determine Exchange health. It detects issues, automatically performs recoveries (Exchange calls these “responders”) and ultimately notifies operators of issues, if the recoveries were not successful. The purpose of this of course, is high availability. Managed Availability is explained in more detail here.
Notification/Alerting to Operations Manager is handled via events, so the Management Pack has a set of simple event monitors that trigger based on these events. Events are logged to the Microsoft-Exchange-ManagedAvailability/Monitoring event log.
First of all, this Management Pack should be simple to implement from an Operations Manager perspective. There are no special components to install on Management Servers, you do not need to worry about the impact to the Management Group in terms of database size, instance space, Management Server workload etc. You should be fine just importing this MP into your existing environment also for large Exchange deployments (as usual, we do recommend gradual deployment just in case). The Management Pack Guide includes a chapter on deployment, as usual you will need to enable Agent Proxy when you install the Operations Manager agents on Exchange 2013 servers.
Also, the Exchange team has been using the same monitoring logic in the Office365 environment. Normally, few changes to the Management Pack should be required.
However, if you should require some adjustments to the Management Pack, you will need to work together with your Exchange administrators.
If you want to disable some monitor, you can just create an override in Operations Manager as usual. This is straightforward.
If you want to change a threshold for some monitor, this is done in the Exchange Managed Availability engine via PowerShell cmdlets. This does not involve Operations Manager at all. The Exchange Management Pack Guide walks through this scenario in some detail here. Since this kind of override is a modification of Exchange behavior, this kind of override is most commonly done by the Exchange administrator.
Also, Exchange Cumulative Updates may contain new or updated monitoring logic. These should be reviewed together with your Exchange administrators to determine the impact of that updated logic.
In terms of interoperability, this Management Pack does not upgrade the Exchange 2010 Management Pack, this is a completely new MP. It is possible to run these Management Packs side-by-side as you upgrade your Exchange environment from 2010 to 2013.
The Managed Availability feature is built in to Exchange 2013. It contains the logic for how to detect issues and how to recover from them. The results of that is then reported to the event log for Operations Manager to pick up via event monitors. This means that updates in terms of Managed Availability monitors are shipped with Exchange Cumulative Updates.
As mentioned previously, the Exchange 2013 Management Pack has functionality to automatically detect these changes, so typically no Management Pack update is required.
Let me know if you have any questions, I will answer the ones I know about and pass other questions back to the Exchange team.
Great work. Huge improvement since 2010.
Anyone know when Exchange 2010 management pack for OpsMgr 2012 will be available?
You can check it out for feedback about the MP.
Just on time !, Great work and efforts to bring this up quickly.
we installed the MP for our in-house monitoring
Is the Exchange 2010 Management Pack being updated? If so, can we expect an overhaul to where it functions similar to this newer MP or will it just include some updates along with official support for SCOM 2012?
Michael and Jon, the Exchange 2010 MP works on Operations Manager 2012 as well. This is on purpose, we don't want people to have to re-write their MPs to work on both versions.
How to track service level with this MP? Most normal MPs rolls up availability health to upper class which then can be used as a trigger for service level. Sorry, I didn't get this MP.
Hi Guntars, the Management Pack has a simple rollup. For example, you should be able to track availability of your servers or organization as usual (check out the provided views).
In terms of reporting, the "health" report should be able to report availability over time for the objects you choose.
Thank you for the response! Could you please demonstrate some examples?
More current (currently maintained) MPViewer version is hosted here blogs.msdn.com/.../boris-s-tools-updated.aspx
I just want to know why there is no reports we really like to reports exchange 2010 Management pack.
is there any plan for bring back reports ?
Why did they take all the reports out of exchange 2013? I have a need to report on transport platform TopUsers, Transport.Platform.ServrStatistics and others. Is ether a simple way to modify these reports to work with Exchange 2013, or am I going to have
design a custom report, or am I just out of luck, any ideas?