Rayan, Please try the instructions in this community article Warm, regards, Peter ... View more

Keith, You should be able to do that today, if I am understanding you correctly.  The only thing that you would not see visualised would be the JMS queue upstream of the 1st tier containing logic. You can, as you suggested, have the last agent in the chain make an end to end latency calculation for the BT configuring an asynchronous transaction demarcator on the last tier that will be involved in the processing.  It is most reliable to use the method instrumentation method to define the logical endpoint. I hope that helps. Warm regards, Peter ... View more

Keith, Queues are currently only depicted on the flowmap if they are downstream of a BT entry.  The queue you see in the picture from the documentation is between the E-Commerce-Services and Order-Processing-Services tiers, and is part of a BT that originates in the E-Commerce-Services tier. I hope that clarifies what you are seeing. Warm regards, Peter ... View more

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

AppDynamics generates an event whenever it detects a JVM restart, if you want to be precise (a quick restart could potentially result in the availability metric never reporting as zero) ... 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

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

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 ... View more

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 ... View more

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 ... View more

Devika, It sounds as if the agent may not be capturing all the thread hand-offs in your application scenario. There could be several explanations for this.  Can you post a screenshot of the waterfall view of a snapshot? Are you using an asynchronous client driver to talk to some backend (maybe a database?) that we do not support out of the box?  That might provide an explanation. (it's important to note that in general peformance issues in applications build using  asynchronous frameworks such as Vert.X often do not manifest as slow code running, but rather as long waits for replies from external services) It will probably be easiest for you to open a support ticket and work through the detail with our support team to identify what is missing if none of the above is helpful. Warm regards, Peter ... View more

Sailesh, You should not need to, since agent logging and application / container logging should be entirely separate.  If you find that not to be the case, I would really appreciate it if you could file a ticket, or post full details of your scenario. That said, you can switch the agent back to using log4j by setting the appdynamics.agent.log4j2.disabled system property to true, but you should not need to do this. Warm regards, Peter ... View more

There were issues with how a few of the early 4.5.x agents used log4j This issue is fixed in any recent 4.5.x agent (the most recent is 4.5.11) If you experience the same issue with v4.5.11 of the agent, please create a new post with details, or open a support ticket. Warm regards, Peter ... View more

Pranay, What do you see in the agent log you will find in the  "/home/ec2-user/apache-tomcat-7.0.82/webapps/appagent/ver4.5.9.25648/logs/<nodename>" directory (where <nodename> is the name of the node you configured) You will likely find some explanation of what is happening in here. Warm regards, Peter. ... View more

Vikas, I am beginning to wonder if your scenario is a JVM crash (i.e. the JVM terminated, due to a JVM bug) or a terminal out of memory error due to insifficient headroom in the heap. For the JVM crash case, you will see a Fatal Error Log.  If you have one of these, please share it. For the out of memory case, you should see one or more java.lang.OutOfMemory exceptions in the application logs.  Alternatively, if you see no out of memory exceptions logged, you could double confirm that memory headroom is not the root cause by setting the JVM to heap dump on out of memory and making sure there is no heap dump created. If you do find a fatal error log, you will need to try and match the symptoms in the log with known JDK bugs.  The fix for out of memory would be to increase Xmx to allow additional operating headroom. Warm regards, Peter ... View more

Vikas, 1.8.0_91 is extremely old (dating from April 2016) and there are a huge number of bug fixes in the subsequent releases. Experience shows that JVM crashes of this kind are almost always fixed by upgrading to the latest JVM version, so I would recommend you try that (and make sure to pay attention to Oracle's licensing changes) Warm regards, Peter ... View more

OK, so the good news is that we have established that your agent installation is fine. Does your spring boot application work fine when the agent is loaded via the command line? What does the "jps -v" command show when it is running? It might be easier to troubleshoot this via a support ticket if we don't uncover anything via the above suggestions. ... View more