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.
- edited on
Content revised 8/1/18
You may want to configure Error Detection to ignore known exceptions. For example, you may see a recurring exception thrown from a framework you are using. If the exception is well-known and insignificant, you might want to eliminate it from the error list.
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:
You can dispose of it by ignoring logged messages such as:
This is the error message:
ItemPersistence : Critical transaction Error, rolling back changes. Order execution aborted.
Below is the configuration for ignoring the error message:
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;
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
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:
at sun.reflect.GeneratedMethodAccessor1249.invoke(Unknown Source)
... <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
java.lang.reflect.InvocationTargetException:com.company.eppi.client.exceptions.ClientException. You would not put it on
The configuration for this example would like the screenshot below:
This is the exception:
Below is the configuration to ignore the error message:
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.
How we can ignore these Exception:
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.
I want to ignore the error below:
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?
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.
Could you open the error snapshot, click on error details and take a screen capture and attach that there.
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"
How can i handle this, same pblm i have, not able to suppress, please advise
Santhosh - are you looking for ignoring errors or exceptions. What is the current ignore rule you have configured.
Could you open the error snapshot, click on error details and take a screen capture and attach that there. If more detailed analysis is needed, please file a support ticket with the above screen captures and current ignore configuration. Thank you
Ganesh, its thrown as exception and in Snap shot i see the following
I am trying to use the exception, i tried w/ and W/o null
Santosh - this will need more detailed analysis. Could you please file a support ticket with the below information:
When you Ignore an exception would appdynamics stop capturing the transaction snapshot of the business transaction where this exception happens or the transaction snapshot would be taken but the exceptions wouldn't visible from the transaction snapshot?
The snapshot will be captured but it will not mark it as error snapshot.
When you configure an exception to be ignored, the agent detects the exception, increments the exception count, and displays the exception in Exceptions lists in the UI, but the business transaction in which the error is thrown is not considered an "error transaction" for monitoring purposes. The transaction snapshot would not show the exception in the Summary or Error Details section and the user experience for the transaction instance would be unaffected by the exception.
More information (source): https://docs.appdynamics.com/appd/22.x/22.2/en/application-monitoring/configure-instrumentation/erro...
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form