Discussion Feed

Avinash,   The notion of a java applicaton (war, ear, etc) does not map to the AppDynamics notion of an application which is intended to model multiple tiers of logic that work together to deliver some higher level goal.   You will need to use BT naming rules to identify your business transactions and if it's useful,  you could use BT grouping to group transactions from different applications.   Warm regards, Peter. ... View more

Avinash,   A since JVM (agent) can only report as a node to one application.   Can I ask what you're trying to achieve?   Warm regards, Peter ... View more

Ganesh,   That is a most surprising observation!     Without digging deeper into what is going on, I am not sure what to suggest.  The best path forward will be to open a support ticket and have a support engineer dig into the details of what is going on.   Warm regards, Peter ... View more

Ganesh,.   You need to set the  appdynamics.agent.tls.allowedAlgorithms  system property on the JVM command line to allow use of TLSv1:    -Dappdynamics.agent.tls.allowedAlgorithms= TLSv1   Warm regards, Peter ... View more

Rohan,   This is an entirely normal scenario, which is discussed in the documentation.   In short, we advise customers to put the common parts of the configuration (e.g. controller URL) in the controller-info.xml file and then provide the parts that vary per JVM as system properties on the command line.   Warm regards, Peter         ... View more

Just to update this thread, since customers have found it and asked for a resolution, since version 4.5.14 of the node agent, the npm install logic for the AppDynamics agent has changed to bring down the platform dependent components in a post-install script.   This means that package lock should no longer prevent Node apps built on one platform being transported to and executed on a different platform (and hence should also remedy this issue with deployment on the Azure platform)   Warm regards, Peter. ... View more