Changing Alert Severity with Overrides

You may often come across situations where you wish to change the severity of an override. Classic example is the infamous 'Script or Executable Failed to run' with a severity of Warning. In large environments, especially where the old school technique of rebooting servers regularly for no particular reason is in place. :-)  One technique I have recommended to my clients is to rather than disable this rather noisy alert, rather tempting, just modify its severity to informational. Although these errors must be dealt with and do occur in large numbers, they definaltey are not urgent. Most of them are traced back to insufficient reosurces, improperly configured WMI or Corrupt Perfmon  objects.

So back to the override, the override is numeric and its value for informational is 0 whereas the default for warning is 1.

0 = INFORMATIONAL
1 = WARNING
2 = CRITICAL

Thanks to Eric Kamor for the information.

Comments

• Anonymous
  January 01, 2003
  I actually blogged about values while back. If someone is interested to see what happens when incorrect value is used, here is such post : http://blogs.msdn.com/mariussutara/archive/2007/12/17/alert-severity-and-priority-use-with-override.aspx