Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
11-13-2020 04:29 AM - last edited on 11-30-2020 02:48 PM by Ryan.Paredez
Hello,
recently I was configuring exceptions and ignore messages guided by this article. I was having the following exception that needs to be ignored
I get the exceptions info from the stack trace was as follows:
SamisWsFault:WebservicesFault:
SamisWSFault:WebServicesFault:.com.ibm.ws.webservices.engine.WebServicesFault <some messages> at
rest of stack trace....
I created three rules to include as follows:
1-
class=SamisWsFault:WebservicesFault:
message=Is not empty
2-
class=SamisWsFault:WebservicesFault:com.ibm.ws.webservices.engine.WebServicesFault
message=Is not empty
3-
class=com.ibm.ws.webservices.engine.WebServicesFault
message=Is not empty
and also I added the messages I want to ignore in the ignore messages sections but I still see these exceptions keep flooding into my applications and apparently these rules didn't work anyone could help me here where I go wrong.
Thanks in advance
^ Edited by @Ryan.Paredez for readability. This conversation was originally on this TKB article: How do I exclude errors and exceptions from detection?
Solved! Go to Solution.
11-18-2020 09:45 AM
Hello, @ahmed.zaki
After some digging, the feedback I've received is that a review of things like debug level logs and error snapshot screen captures would be needed. Thus, could you open a Zendesk case?
My ask for the Community is that you come back and tell us what you learned!
Kind regards,
Claudia
11-30-2020 03:04 PM
Hi there,
Regarding class=SamisWsFault:WebservicesFault:com.ibm.ws.webservices.engine.WebServicesFault
Are SamisWsFault and WebservicesFault classes? If so, try specifying the full class paths e.g.
xxx.xxxxx.SamisWsFault:xxx.xxxx.WebservicesFault:com.ibm.ws.webservices.engine.WebServicesFault
All of the Exception classes from an error need to be in the colon delimited list. A good way to see them all is in a transaction snapshot-> Slow Calls and Errors -> Errors, rather than the Troubleshoot-> Errors-> Exceptions list which just displays a single error
Mark
User | Count |
---|---|
5 | |
4 | |
3 | |
1 | |
1 | |
1 |
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form