Health monitoring - disabling monitors vs. probes.

Hi,

If you go in to your Exchange server health and find a monitor unhealthy, all the instruction clearly states that if it is a known issue, you should just disable that MONITOR.

However, without the monitor, what is the point in leaving the PROBE running?

To me, on the surface, it feels a bit like driving home and going in for the night, but leaving your car engine running all night. Seems pointless to me. If the probe is running, doing its checks, but you are not monitoring it and can therefore also not use the resolver, why not override the probe for the faulting monitor.

It may be that the probe is still useful, for event logging or something, not sure, but confirmation would be good.

The real reason this came about, is I have seen a very odd issue come up which is as follows.

We saw an unhealthy monitor, it was not needed and everything on the internet said to disable it. We did that and that was fine - however, we were seeing a high CPU issue. We took the override off and CPU returned to normal. We then disabled the PROBE for this monitor and the error was gone and CPU remained normal.

Any idea what could cause this? It seems to suggest that the Probe, without the monitor doing it's thing, was causing high CPU.

I'll confirm the exact monitor / probe shortly. But on principle, if you have a dodgy monitor, why not cut it off at the source and disable the probe?

Thanks

James

September 14th, 2015 4:23am

Hi James,

Please provide more details on the probe where you have seen this. Also links to the sites asking to turn the monitor off.

Free Windows Admin Tool Kit Click here and download it now
September 14th, 2015 6:41am