You are right on the money. Things like datasource criteria are not exposed via overrides. To modify the datasource criteria - you need to disable an existing workflow, then recreate your own in a similar fashion.
In your specific example - you should not generally use "event description contains". You should figure out which parameter the object is filled in as - and then add your criteria line of "Param 6 does not equal FOO" or something like that. From: [email protected] [mailto:[email protected]] On Behalf Of Gilmanov, Nile Sent: Monday, June 30, 2014 4:43 PM To: [email protected] Subject: [msmom] Override Question Guys, I am getting a Critical alert for a given task in the SQL Management Pack. Details: Alert Source: MsDtsServer100 Log-name:Application Description: Package "blah-blah" failed. When I go to create an override, it does not give me a Description parameter and I cannot edit the RULE that it's using. All I need to do to the rule is to add an exception in the form of EXCEPT WHEN EVentDesc. Contains "blah-blah" formerly stated. After some research it looks like I have to: 1. Create an override to disable that MONITOR/RULE (expression) for the specific object (in my case I created a group and stuck the server in there). 2. Create my own monitor (application log monitor), basically re-create what was there from the Sealed MP but add a condition (except for BLAH BLAH package in Event Description). Thus the end-result is that we are not getting alerts for that specific package. Am I on the right track? Any other solutions to this seemingly common dilemma? Thank you! Nile
