Knowledge Base

Showing results for 
Search instead for 
Did you mean: 

How do I exclude errors and exceptions from detection?

Updated on 8/1/18


You may want to configure Error Detection to ignore a number of known exceptions. For example, you may see a recurring exception that is thrown from a framework you are using. However, the exception is well-known and insignificant so you want to eliminate it from the error list.




What you need to know about each error

The first thing you need to know for each message is whether AppDynamics is detecting it as a thrown exception or a message written to a log file with severity ERROR. If it is an exception, the snapshot's Error Details tab should have a stack trace. If you only see the error message, it's a logger.


Example: Logged error message:Screen Shot 2018-06-28 at 1.25.21 PM.png


You can dispose of it by ignoring logged messages such as:File not found logged error message.png


Ignoring Error Messages Example

This is the error message:
ItemPersistence : Critical transaction Error, rolling back changes. Order execution aborted.


Ignoring Error Example 1.png


Below is the configuration to ignore the error message:

Configuration to ignore the error message.png


Excluding Exceptions Examples

The next two examples are thrown exceptions, both from the same place:

Response-xslFile :null; IsActivationCompleteSuccess:false; IsValidated :false; 
OrderType :QUERY; AccountNumber :null; CustomerQualification :null;
CapErrorCode :00602; capErrorType :1; CapErrorCategory :CDE; CapErrorDesc
:Account_Data_Discrepency; OperationMode :null; OperationStatus :null;
ActivationDate :null

SUBMIT_ACTIVATION_DETAILS : Transaction Id:xx-23341105-1 -
Controller:handleRequest() > An Exception is caught
Dependent object contains ... [details deleted] CarrierErrorCode
The exception message is
Controller:handleRequest(): Transaction failure response from


You can exclude these by specifying as the class and ignoring particular values of CarrierErrorCode (which are buried in the full message).


If it is a true exception, please note whether it's nested inside another exception. You'll need to specify the exact sequence in the Error Detection config. It will look like this: : Controller:handleRequest(): Transaction failure response from Carrier.


Pay close attention to what is in the stack trace. For example, a stack trace similar to the following might show up in the Error Details section of a snapshot:
at sun.reflect.GeneratedMethodAccessor1249.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(
... <details deleted>

Caused by: com.comodo.epki.client.exceptions.ClientException :
com.comodo.epki.client.exceptions.ClientException: Not authorized agent


Don't create the exclusion on the "caused by" exception. Instead, use the first one in the stack trace. In the example above, you would set the Fully Qualified Class Names for Exceptions field as You would not put it on


The configuration for this example would like the screenshot below:  



Ignoring Exceptions Example

This is the exception:



No Such Element Exception.png

Below is the configuration to ignore the error message:

Configure an exception to ignore the error.png


Related Documentation

For more detailed information on error detection and specifically how to ignore exceptions and log messages, see: Ignore Exceptions and Log Messages as Error Indicators.

Version history
Revision #:
15 of 15
Last update:
‎09-14-2018 01:06 PM
Updated by:

Found this article helpful? Click the Thumbs Up button.
Have an additional comment? Post it below.