{"id":1409,"date":"2012-10-08T01:08:32","date_gmt":"2012-10-07T23:08:32","guid":{"rendered":"https:\/\/alax.info\/blog\/?p=1409"},"modified":"2012-10-08T01:12:31","modified_gmt":"2012-10-07T23:12:31","slug":"log-process-exceptions-filters-and-email-notification","status":"publish","type":"post","link":"https:\/\/alax.info\/blog\/1409","title":{"rendered":"Log Process Exceptions: Filters and Email Notification"},"content":{"rendered":"

Moving on with LogProcessExceptions<\/a> tool which externally monitors (debugs, to be more specific) an application of interest and captures its exceptions writing minidump files<\/a> for further analysis.<\/p>\n

This updates adds two features:<\/p>\n

    \n
  1. Ability to filter out the exceptions of interest<\/li>\n
  2. An email notification on exception, with or without minidump file<\/li>\n<\/ol>\n

    Filter<\/h2>\n

    A new property page in the wizard provides one with an option to specify filters\/rules to identify exceptions of interest. One rule per line, once exception occurred its codes are compared against rules top to bottom. The first matching rule results in decision whether to log the minidump (and issue a notification) or not. If no filter\/rule applicable found, or the entire filter is empty, the exception is logged (positive).<\/p>\n

    \"\"<\/p>\n

    The rule syntax is the following:<\/p>\n