Exception filtering not working as expected

[CommunityUser]

Hi, 

I'm working on filtering out some of false errors we are getting on our BTs and so far my configuration for ignoring exceptions when detecting errors is not performing as I would expect. 

Here is what I'm trying to accomplish, I'm seeing a lot of transaction snapshots reporting as errors with a stack trace that looks something like this:

java.lang.reflect.InvocationTargetException:javax.xml.ws.soap.SOAPFaultException:

java.lang.reflect.InvocationTargetException.null
      at sun.reflect.GeneratedMethodAccessor288.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:606)
<Details Removed>
...

 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
      at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.reflect.InvocationTargetException : javax.xml.ws.soap.SOAPFaultException: Password mismatch[password mismatch]

In this example we are sending a SoapFaultExample back to a front end from a service designed to verify user credentials. This is a fully expected result (user credentials were not correct) and we don't want it to register as a Error in AppDynamics. 

I found the knowledge base article How To Exclude Errors and Exceptions from Detection by AppDynamics that appears to be very simular to what I'm trying to accomplish but so far I've had no luck.

Per the article I set my ignored exception up like this:

Using the full path of the exception class detecting a empty message. After saving this and clicking "Save Error Configuration" I'm still seeing this exception show up as a errored BT.

I've also tried the following configurations:

With all of these configurations my transactions are still showing a "User Experience: Error" status.

Ultimately I would like to be able to exclude SOAPFaultExceptions based on the error message like is shown in the third example. We have exceptions that are white listed (such as Password Mismatch) and others that we would like recorded as errors so I'm hoping there is a way to filter based on the message. 

Any ideas why my transactions are continuing to be marked as errors even after excluding the exception?

Thanks!

[Arun_Dasetty]

Hi,

Can you quickly try below options and if issue persists, send the exported snapshot pdf and <agent_install_dir>/logs for our reivew?

change equals to (contains) option for "exception message" field Or try option "matches reg ex" with value .*

(read as dot symbol followed by asterisk once)