Discussion Feed

Mark.Byrne · ‎11-30-2020

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

Mark.Byrne · ‎06-15-2020

Hi Bojan, I can confirm that it doesn't show anymore with the 20.6 version - we received the SaaS upgrade last week. Mark

Mark.Byrne · ‎04-30-2020

Hi Blaine, We've raised a support request for this, and have had acknowledgement that the UI team are looking at a better way of doing this. Mark

Mark.Byrne · ‎04-29-2020

Hi there, It sounds like you have hit the limit on custom metrics. Take at look at this article: https://docs.appdynamics.com/display/PRO45/Configuring+Custom+Metrics It has advice on increasing the limit, up to a max of 150. Regards Mark

Mark.Byrne · ‎04-19-2020

Hi there, I believe the NetVizAgentRequest error is not being able to connect to the Network Visibility agent.We get this error all the time for agents that work fine. If you are having problems connecting to your controller then I would recommend ignoring all the NetVizAgentRequest errors, and looking for a different error message. Mark

Mark.Byrne · ‎02-20-2020

Thanks, We raised it with AppD as well, and they managed to find a single occurrence of an anomaly in our controller. It was extremely deviant from baseline, and the health rules we had set up noticed it sooner than the anomaly triggered. Mark

Mark.Byrne · ‎02-19-2020

Hi Deepak We are experiencing the same thing - no anomalies despite Health Rules being triggered. Did you ever get an answer to your question? Thanks Mark

Mark.Byrne · ‎01-22-2020

Hi Arun, If you have an on-prem controller, I would have suggested trying to add the certificate to the keystore of the server. It looks like someone else has run into this problem, tried to do this, then had subsequent problems. You could perhaps try something similar? https://community.appdynamics.com/t5/Controller-SaaS-On-Premise/HTTP-Request-failing-due-to-self-signed-cert-on-target-server/td-p/34697 Mark

Mark.Byrne · ‎01-21-2020

Hi Arun, By the looks of things you are trying to send an alert to a HTTPS server that is using a certificate that has not been signed by one of the main Certification Authorities - is it perhaps self signed? Mark

Mark.Byrne · ‎01-16-2020

Hi Bill, We have done this, but used a shell script to make the calls to the Controller API and store the output into files, then had the logstash file plugin ingest them into Elastic. Mark

Date Registered	‎07-02-2019 04:30 PM
Date Last Visited	‎12-23-2020 11:38 AM
Total Messages Posted	22
Total Kudos Received	24

Discussion Feed

Re: How do I exclude errors and exceptions from de...

Re: database not connected showing constantly on t...

Re: How do we turn off the message stating there a...

Re: Maximum Custom Metric limit is reached

Re: Error =- Unable to get application report to c...

Re: Anomaly Detection not reporting any Anomalies

Re: Anomaly Detection not reporting any Anomalies

Re: PKIX path building failed

Re: PKIX path building failed

Re: Exporting metric information into Elasticsearc...