Configuring or Disabling Replication Monitoring in the Active directory Management pack

JIMMY HARPER'S OPERATIONS MANAGER BLOG : Configuring or Disabling … | Webmaster Tools

Wed, 20 May 2009 10:41:45 GMT

PingBack from http://www.netdeluxo.com/blog/blogs/jimmy-harpers-operations-manager-blog-configuring-or-disabling/

re: Configuring or Disabling Replication Monitoring in the Active directory Management pack

Steve Burkett — Wed, 02 Sep 2009 19:18:57 GMT

Great info thanks Jimmy! If we're getting some 'AD Replication is occuring slowly' alerts for some of our DC's and that's normal as they're on the other side of the world etc, what should we be overriding (x 14)? The 'For a specific object of class: Active Directory Domain Controller Server 200x Computer Role' for the DC that's reporting the error? Or do we just take the largest latency we see and set that for all of them?

re: Configuring or Disabling Replication Monitoring in the Active directory Management pack

jimmyharper — Fri, 04 Sep 2009 09:27:04 GMT

You'll need to take the largest latency and set that for all of them. Unfortunately, we don't have a way to set latency for replication FROM a specific DC. Now, if replication TO a specific DC (FROM all other DCs) is different than others, you can set a high intersite latency threshold for just that DC.

Also, note that we only alert if the replication time is 3 times the latency threshold, so you could set it a bit lower than the largest latency that you see for those sites.

Another option would be to just not monitor Replication from those far off DCs....just set overrides to disable the rules on those DCs, and remove their objects from OpsMgrLatencyMonitors container from Active Directory (remember to remove it from each Directory partition that you are monitoring)

re: Configuring or Disabling Replication Monitoring in the Active directory Management pack

Andy S — Fri, 04 Sep 2009 16:17:18 GMT

Thanks for this information, this was really starting to annoy me. I had already identified a few of the rules manually, but sometimes those XML files just can be hard to read. I do understand tat this is by design, but honestly I think that this is a flaw in a monitoring system if I have to create 14 overrides to configure something like that. Especially treshold you modify after you get a feeling for it, so if my first guess wasn't right or something changes I have to do it again. And just imagine if I want to configure it differently based on server or site - I'd probably waste less time monitoring the replication manually for an entire year by running one quick command every morning, and this almost defeats the purpose of making things easier.

Maybe a next version can have some kind of "Meta-Rule" or "Meta-Monitor", that would allow us to apply Overrides to a whole set of rules and monitors would help in situations like that. The MP author can then group certain objects together, and the Operator will only need to remember one Meta-Rule, e.g. "AD Replication latency". Because really, the allowed replication time is independant of the OS I am running, so having different sets of rules based on OS is somewhat illogical.

re: Configuring or Disabling Replication Monitoring in the Active directory Management pack

Steve Burkett — Wed, 09 Sep 2009 11:31:20 GMT

Great, thanks Jimmy, shall experiment with this one. While I've got ya, is there any tweaks we can do to make the management pack (Replication monitoring and otherwise) more resilient on WAN connections that drop out occasionally for a minute or two? Ie. Not be so hasty to fire off alerts.