KBI 311552 Issue Addressed: File Log Rule Checking Specific Event Does Not Exist Could Not Resolve Automatically Or Reset Occurrence


Argent Advanced Technology 5.1A-1704-B or earlier


Thursday, 29 June 2017


When File Log Rule uses option ‘Rule Is Broken If The Specific Event Does Not Exist’, it cannot be resolve automatically. For example, if the specific event does not exist during the lookback minutes, the Rule is broken correctly. In next check, the specific event shows up in the log, the Rule is no longer broken. However, the event won’t be resolved automatically, which is incorrect.

Also, if Rule uses option ‘Post Event Only After The Rule Is Broken xxx or More Times’ and reset occurrence counter option ‘After Condition Is Corrected’, the Rule won’t function properly. For example, event should be post after Rule is broken 3 times in the row. The Rule is broken two times in the row, but not broken in the 3rd time. Rule is broken at 4th time; event is post while it should not. The issue is that the 3rd check does not reset the occurrence count back to zero due to the issue.

The issue has been addressed in Argent AT 5.1A-1707-A.

Technical Background

This is caused by coding error.


Upgrade to Argent Advanced Technology 5.1A-1707-A or later.