KBI 311349 Issue Addressed: Event Is Not Automatically Corrected For Performance Rules Containing Keyword OR


Argent Advanced Technology 3.1A-1601-C and earlier


Tuesday, 16 February 2016


A broken Performance Rule containing keyword ‘OR’ might not be automatically corrected even the Rule is no longer broken for any Performance instance

A sample Rule looks like following:

The issue happens with or without option ‘Fire Separate Events For Each Performance Instance’ being used

Because the outstanding Event is not automatically corrected, besides the common symptoms including Event not resolved, condition resolution Alerts not fired and escalation not stopped, one less common symptom is that the Relator keeps running on specified checking interval instead of returning to the normal Relator schedule

The issue has been addressed in Argent AT 3.1A-1601-T2

Technical Background

The issue was caused by mismatched Event comparison string when keyword ‘OR’ was used

Because the comparison string when Rule was no longer broken did not match fired Events, the outstanding Events could not be resolved automatically


Upgrade to Argent AT 3.1A-1601-T2 or later

For customer who cannot upgrade immediately, he can break the current Rule into two separate Rules without using keyword ‘OR’

For example, the sample Rule can be break into two with criteria: