I suggest you ...

Bug in AD MP - Domain Member Global Catalog Performance Data Source

Issue exists in current version 10.0.2.1 of the MP.

In the "Microsoft.Windows.AD.DomainMemberPerspective.Performance.GlobalCatalog.DataSource" datasource, there is a simple bug that is breaking both the AD Member GC Performance Monitor, as well as the Performance collection that also uses this DS. The timer in the script calculates the time in seconds:

iTime = DateDiff("s", dtStart, Now)

Unfortunately, the value is returned to the property bag only after the value is divided by 1000:

Call oBag.AddValue("StatusValue", "" & iTime / 1000)

The thresholds in the monitor are intended to be seconds, so this is an obvious mistake. You can easily validate this by looking at the performance data returned from the associated rule as well. It shows .001 when the actual response time was 1 second.

1 vote
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Chris McIntyre shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base