KBI 311003 Issue Addressed: Performance Rule Wrongly Use Local Disk Metric When Target Machine Does Not Have The Disk


Argent Advanced Technology 3.1A-1404-A or earlier


Thursday, 10 July 2014


If Performance Rule is configured to check a single logical disk, such as Drive E: in following example, it can read wrong Disk Metric when the target machine does not have the disk

The issue does not happen if wildcard or regular expression is used to check multiple drives

The issue has been addressed in Argent AT 3.1A-1404-T5

Technical Background

When target machine does not have the disk, the Performance Counter API apparently won’t be able to read the metrics for the disk

Argent AT uses API ‘GetDiskFreeSpaceEx‘ as the fall-back method to read logical Disk Metrics

Unfortunately the API has a bug when drive letter is used

By using a UNC path of a share on the disk will solve the issue


Upgrade to Argent Advanced Technology 3.1A-1404-T5 or later