Discussion Feed

Peter.Holditch

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

Peter.Holditch

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

Peter.Holditch · ‎10-17-2019

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

Peter.Holditch · ‎10-08-2019

@Just.Someo I'm afraid it is only possible to pass constant parameter values to methods in getter chains so there is no way to achieve what you want by this route. Is there any way you can change the application code to programatically collect the data you need using the java agent API? Warm regards, Peter

Peter.Holditch · ‎09-17-2019

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.

Peter.Holditch · ‎09-09-2019

Surendra, This is very strange. If the agent is not generating any output or log files, it is almost certainly not getting loaded for some reason. What do you see if you run: java -Xmx1024m -javaagent:/opt/appdynamics/appserver-agent/javaagent.jar -Dappdynamics.agent.applicationName=xxxx -Dappdynamics.agent.tierName=xxx -Dappdynamics.agent.nodeName= xxx-api_xxxx001 -version Do you see anything at all in the 'tiers and nodes' dashboard of your application?

Peter.Holditch · ‎09-08-2019

Surendra, Try moving the -javaagent and the -D options ahead of the "-jar" option in your command line. Warm regards, Peter

Peter.Holditch · ‎09-08-2019

Tan, I am afraid I don't have a good answer for you today, but I am interested in your use-case. Where does your label come from? What does it mean to you? What do you want to do with the nodes once tagged? (I assume you want to slice them in some way; for what purpose?) can you arrange for your tag to be included in the AppDynamics node name? I wonder if that might help you achieve your objectives here? Warm regards, Peter

Peter.Holditch · ‎09-05-2019

The logs are empty, or no logs are created? If the latter case, do you see any output from the agent on stdout/stderr as the JVM starts? Can you post the output of ps -ef for your java process? What do you see if you take your agent options and just run java <your-options> -version ? Warm regards, Peter

Peter.Holditch · ‎09-05-2019

Surenda, What do you see? Do you see any logs written in the agent logs directory? Any node reporting to your application in the "Tiers & Nodes" dashboard? The agent logs will be the most useful source of troubleshooting information Warm regards, Peter

Date Registered	‎01-23-2013 01:54 AM
Date Last Visited	Saturday
Total Messages Posted	289
Total Kudos Received	58

Discussion Feed

Re: Application was unable to connect to database ...

Re: Application was unable to connect to database ...

Re: Java agent implementation

Re: Java Data Collector method getter chain

Re: `NPM install` integrity check failure on Linux

Re: MicroServices V3 Monitoring

Re: MicroServices V3 Monitoring

Re: Add custom tag field to APM agent?

Re: MicroServices V3 Monitoring

Re: MicroServices V3 Monitoring