Version

Argent Advanced Technology 3.1A-1401-A or below

Date

Friday, 31 Jan 2014

Summary

If Windows Performance Rule is configured without option ‘Fire Separate Events For Each Performance Instance‘, when Rule is broken, the event message only shows the first performance instance that breaks the Rule; when Rule is corrected, the auto correction message shows only the last performance instance checked

As a result, the auto correction message may show mismatching instances for corrected condition and original event

Technical Background

For example, a Disk Free Space Percentage Rule is configured as following:

Click For Full Size

The target machine has drives C:, D: and F: with free space 10%, 30%, 25% respectively

When Rule runs against it, it reports drive C: has 10% free space lower than threshold

Later customer frees up spaces in C: drive, and now it is 40% free

When Rule runs again, it will loop through all the drives, and find all has free space more than threshold

The condition has been corrected

But it sends out the notification message as:

Though technically the corrected condition is reported correctly, the notification message is confusing

Argent AT 3.1A-1401-B has been enhanced to include all the instances in the re-check result so the original culprit instance is definitely included

Resolution

Upgrade to Argent AT 3.1A-1401-B or later

Customers who cannot upgrade immediately may check the option ‘Fire Separate Events For Each Performance Instance‘ in Performance Rule

In most cases, it is a preferred setting as each instance is checked and corrected individually