Discussion Feed

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

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

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