Discussion Feed

Mario.Morelli · ‎11-28-2021

Hi The error you see is related to Network visibility. By default the Java agent is trying to send data to the Network Visibility agent on the server that it's running on. If the network visibility agent is not installed/running, you will see this error. I believe in the latest release of the agent java agent this value is set to false by default, to not generate this error. Technically this should not interfere with the Java agent itself and would just fill up the logs with unnecessary errors. To stop this error from occurring you can set a agent node property to tell the java agent to not send data to the NetViz agent as its not installed and/or running. Or you can install the NetViz agent if you want to accept the data from the Java Agent. https://docs.appdynamics.com/21.11/en/application-monitoring/administer-app-server-agents/app-agent-node-properties-reference/app-agent-node-properties-s Node Agent property below name : socket-enabled type : boolean value : false Save and apply to the agent. Ciao

Mario.Morelli · ‎11-22-2021

Hi Murali AppDynamics does support JDK 11 upwards - https://docs.appdynamics.com/21.11/en/application-monitoring/install-app-server-agents/java-agent/java-supported-environments We have some issues with version 21.10 of the agent as well, can you use a version below e.g 21.9 and test to see if it works?

Mario.Morelli · ‎11-15-2021

Hi Shubhangi The SNOW data Sync Utility can be installed on any server, as long as the host has connectivity to both the target ServiceNow® instance and the target AppDynamics Controller. It can be installed on a standalone server, or you can run it from another server already in your environment. It integrates the topology into SNOW, which then is available inside SNOW to be able to map out topology and log events against. If the server that runs the data sync utility goes down, the topology sync would no longer occur. However this would only affect any new topology that has been created in AppDynamics that has not been synced to SNOW yet It is clearly explained in the below link https://docs.appdynamics.com/21.9/en/extend-appdynamics/integration-modules/integrate-appdynamics-with-servicenow-cmdb-and-event-management Ciao

Mario.Morelli · ‎11-10-2021

Hi Mohamed You can try a data collector like below and assign it to the business transaction to be extracted, which should return the userId value, you can adjust it to extract any of the values if you require it. ToString().Split(string/"userId": ).[1].Split(string/,).[0] Ciao

Mario.Morelli · ‎10-28-2021

Hi Murali AppD supports JDK 11 up to 16 on most of the platforms, can you advise which version of the Agent you downloaded and used? Don't see why it would be an issue itself Ciao

Mario.Morelli · ‎10-25-2021

Awesome Dale Easiest way would be to check if you can archive a "Normal Event", to see if the API works at all. But yes, best would be to check with AppD Support if that is the case. Might just be an omission from the documentation that its auto archived. Ciao

Mario.Morelli · ‎10-23-2021

Hi Dale I don't believe there is an official API for it, that I know of. To get the API that is being called just use developer tools in your browser, and archive an event. You will see a specific API that's called, with an input of the EventID that is being archived. You can then just build that into your process, when you create a deployment event, to immediately archive it. Ciao

Mario.Morelli · ‎10-13-2021

Hi Dale in reality there is no real difference, as both are built on Java, it's the agent itself that is unable to connect There is only one reason I can see, other than if there are communication problems between the server that Tomcat runs on and the Controller. I see you have added all the controller config as properties, but the setting for the below is missing, which is needed if you are using a secure port like 443 for SSL/TLS -Dappdynamics.controller.ssl.enabled=true A possibility with the previous Websphere agent might be that you added the setting in the agent's controller-info.xml file or it was overlooked when you copied the configuration over to Tomcat. Ciao

Mario.Morelli · ‎10-12-2021

Hi Team Just wanted to know if anyone has built a custom extension to gather disk latency stats using the Machine agent or via an extension for Linux? The default SIM metrics don't have this info, and we don't need the I/O Utilization Thanks

Mario.Morelli · ‎08-30-2021

Hi Tom You can do it this way SELECT transactionName, count(*) AS "Counts" FROM transactions WHERE userExperience = "ERROR" ORDER BY Counts DESC LIMIT 5 This would be across all applications, you can put in additional filters if you want to limit it to a specific application etc. Ciao

Date Registered	‎07-03-2019 02:39 AM
Date Last Visited	‎11-30-2021 05:40 AM
Total Messages Posted	170
Total Kudos Received	119

Discussion Feed

Re: Java agent not responding to Payara

Re: Error in configuring javaagent in Spring Boot ...

Re: Where does the data sync utility for ServiceNo...

Re: Grab a specefic property from a session object

Re: Error in configuring javaagent in Spring Boot ...

Re: Is there an API in AppDynamics that can be use...

Re: Is there an API in AppDynamics that can be use...

Re: Java agent on Tomcat receiving "Connection Ref...

Disk Latency

Re: How to create an Analytic query that would sho...