This parameter will appear only if the ADVANCED SETTINGS flag is set to ‘true’. By default, this test flags the transactions in which the following errors/exceptions are captured, as Error transactions:
- All unhandled exceptions;
- Both handled and unhandled SQL exceptions/errors
This implies that if a programmatically-handled non-SQL exception occurs in a transaction, such a transaction, by default, will not be counted as an Error transaction by this test.
Sometimes however, administrators may want to be alerted even if some non-SQL exceptions that have already been handled programmatically, occur. This can be achieved by configuring a comma-separated list of these exceptions in the INCLUDED EXCEPTIONS text box. Here, each exception you want to include has to be defined using its fully qualified exception class name. For instance, your INCLUDED EXCEPTIONS specification can be as follows: java.lang.NullPointerException, java.lang.IndexOutOfBoundsException. Note that wild card characters cannot be used as part of your specification. Once the exceptions to be included are configured, then this test will count all transactions in which such exceptions are captured as Error transactions.