cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

Knowledge Base

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.

 

Contents

 

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:

com.appdynamicspilot.persistence.ItemPersistence.com.appdynamicspilot.persistence.
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
:null;
The exception message is
:com.company.bb.cap.exceptions.CarrierBusinessRulesException:
Controller:handleRequest(): Transaction failure response from
Carrier.

 

You can exclude these by specifying

com.company.bb.cap.exceptions.CarrierBusinessRulesException 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:

java.net.WebException : com.company.bb.cap.exceptions.CarrierBusinessRulesException: 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:

 

java.lang.reflect.InvocationTargetException:com.company.eppi.client.exceptions.
ClientException:
java.lang.reflect.InvocationTargetException.null
at sun.reflect.GeneratedMethodAccessor1249.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
... <details deleted>

at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: com.comodo.epki.client.exceptions.ClientException :
com.comodo.epki.client.exceptions.ClientException: Not authorized agent
at
com.comodo.epki.extra.agent.ws.CcmExtraAgentServer.authorizeAgent
(CcmExtraAgentServer.java:210)
at
com.comodo.epki.extra.agent.ws.CcmExtraAgentServer.getExtraCommand
(CcmExtraAgentServer.java:70)

 

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 java.lang.reflect.InvocationTargetException:com.company.eppi.client.exceptions.ClientException. You would not put it on com.company.epki.client.exceptions.ClientException.

 

The configuration for this example would like the screenshot below:  

exclude-exception.png

 

Ignoring Exceptions Example

This is the exception:

org.springframework.transaction.CannotCreateTransactionException:org.eclipse.persistence.
exceptions.DatabaseException:org.apache.tomcat.dbcp.dbcp.SQLNestedException:java.util.
NoSuchElementException

 

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
Last update:
‎09-14-2018 01:06 PM
Updated by:
By replying you agree to the Terms and Conditions of the AppDynamics Community.
Comments

How we can ignore these Exception:

 

java.lang.NullPointerException

java.lang.NullPointerException.null

at abc..xyz

at abc...xyz1

@Urvershi.Anand ,

Are the BTs being marked as error BT due to those exceptions which you mentioned? If so, could you provide the screen capture as shown above for the error snapshot along with what has been configured to ignore the exceptions.

 

We might need to perform more detailed analysis after reviewing the above requested information. At that point, would recommend filing a case/ticket.

 

Thanks,

Ganesh

Hi All,

 

I want to ignore the error below:

java.sql.SQLIntegrityConstraintViolationException
ORA-02291: integrity constraint (AO_EP.FK_PROFILE_CUSTOMER) violated - parent key not found
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
 
..
 
For doing so, I've added the ignore messages as below:
VincenzoBarra_0-1629921341696.png

Even doing so, those snapshots having such error are still tagged as "red".

Am I doing something wrong? Are those configuration changes supposed to take effect immediately or require some restart?

 

Regards,

Vincenzo


PS: I also tried to add "Ignored Exception" specifying the fully qualified exception as "java.sql.SQLIntegrityConstraintViolationException" and the message to ignore as  "Contains" "integrity constraint (AO_EP.FK_PROFILE_CUSTOMER)", also in such case the calls are still marked as red.



Hi @Vincenzo.Barra 

Could you open the error snapshot, click on error details and take a screen capture and attach that there.

 

Thanks,

Ganesh

Hi @Ganesh.Magal,

 

it worked after we used the ignore exception and rather than putting the whole message only a portion of it such as "contains" "AO_EP.TCUSTOMER_SHARED_ID_TYPE_UNIQ"

 

Regards,

Vincenzo

 

VincenzoBarra_1-1630432160672.png