Spectrum Event Configuration rules not triggering event

Products

• CA Spectrum

Issue/Introduction

Event Condition rules that uses regexp do not trigger custom events used to create or clear specific alarms.

From the AlertMap file the deviceHealthCheckTrap is defined as follows: 

# deviceHealthCheckTrap deviceHealthCheckMessage 
1.3.6.1.4.1.3417.2.7.2.6.1 0x05610002 1.3.6.1.4.1.3417.2.7.1.1.1(1,0) 

In the $SPECROOT/Events/EventDisp file, the event 0x05610002 has been customized as follows:

0x5610002 E 20 R CA.EventCondition,
"(regexp({v 1}, {S \"^.*\b(Channel-Integration-HBS-ACE-device-LST-VIP)\b.*\b(changed from: OK, to: Check failed)\b.*$\"}))" , "0xfff00087  -:-",
"(regexp({v 1}, {S \"^.*\b(Channel-Integration-HBS-ACE-device-SV&I-VIP)\b.*\b(changed from: OK, to: Check failed)\b.*$\"}))" , "0xfff00088  -:-",
"(regexp({v 1}, {S \"^.*\b(Collect-and-Return-ACE-LST-VIP)\b.*\b(changed from: OK, to: Check failed)\b.*$\"}))" , "0xfff00089  -:-",
"(regexp({v 1}, {S \"^.*\b(Collect-and-Return-ACE-SV&I-VIP)\b.*\b(changed from: OK, to: Check failed)\b.*$\"}))" , "0xfff0008a  -:-",
"(regexp({v 1}, {S \"^.*\b(GoDaddy-S1)\b.*\b(changed from: OK, to: Check failed)\b.*$\"}))" , "0xfff0008b  -:-",
........

However, the customer events 0xfff... are not triggered...
 

Environment

Any Spectrum version

Resolution

Work-around: remove all \b (a word boundary) from the regexp string.

Even if the \b can be coded in regexp, Spectrum does not like it and causes the regexp to fail.

Removing the \b from regexp string ie.

from:

regexp: ^.*\b(Collect-and-Return-ACE-LST-VIP)\b.*\b(changed from: Check failed, to: OK)\b.*$

to:

regexp: ^.*(Collect-and-Return-ACE-LST-VIP).*(changed from: Check failed, to: OK).*$

and updating Events on the VNM model solved the issue.