Brandy, I'm not sure that field will work the way you are expecting. I'm under the impression that this field is considering all text to be in the field. So you'd only get alerts with "NOT LIKE %SQL%" in the description field; not alerts that don't have "SQL" in the description.
If I'm getting the gist of what you are trying to do; your intent is to only alert when NEW, CRITICAL(LOW) alerts raised by the rule or monitor "xMatters Validation" and aren't "SQL related" occur. My question is, are any of the xMatters validation rules/monitors running against SQL object types? If no, then I don't think you'll have anything to worry about. If yes, then you need to re-strategize this notification subscription. Consider overriding alerts from SQL sources to not meet this criteria (Warning/High) or just turning off these rules/monitors for the undesired object type. Thanks, Blake From: [email protected] [mailto:[email protected]] On Behalf Of Brandy Reid Sent: Thursday, November 13, 2014 1:29 PM To: [email protected] Subject: [msmom] NOT LIKE Statements in Notification Subscriptions Hi Forum, I'm trying to build a subscription that includes a NOT LIKE Statement but I can't get it to work. Has anyone had success using NOT LIKE in their subscriptions? I've attached a screen shot.. [cid:[email protected]] Thanks, Brandy Brandy Reid | System Admin II | Information Technology | BMHCC - CORPORATE Phone: (901) 227-3061 | [email protected]<mailto:[email protected]> Opinions expressed above are not necessarily those of Baptist. This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email...
