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

Sorry, my mistake, I reversed the options. What happens when you run: "java -javaagent:D:/Applogs/appagent/javaagent.jar -version" ... View more

Do you see any agent logs written under D:/Applogs/appagent/ver4.x.y.x/logs/<nodename>? What happens if you run "java -version -javaagent:D:/Applogs/appagent/javaagent.jar"  from the command line? ... View more

The correct option to load an agent into the JVM is "-javaagent", not "-Djavaagent" I hope that helps.  If not, please post full detail of your command line. ... View more

Jeremy, What agent version are you running?  With 4.4.2 or later, the thread dumps should be consumable by any tool (e.g. the IBM analyser you mention, or Samurai) If you are runnng an agent version higher than that, please provide a thread dump and the precise tool version you are trying to use to read it. Warm regards, Peter ... View more

Chris, AppDynamics APM agents are orientated aroud identifying, measuring and alerting on server side activity.  In our model, the server side activity is classified into Business Transactions which are tracked end to end through the architecture. If yours is a web application, and you want to track the user experience all the way from the end user's device, then you will indeed need to deploy end user monitoring agents to capture the client side perspective (which of course, links to the server side activity to give true end to end visibility. Warm regards, Peter ... View more

Rohan, Do you have any application processes instrumented with an application agent running on the "appdpod2-app" machine? To be automatically associated with an applicaton, the machine agent needs to coexist with at least one application process on its host. If not, you can manually make the association through configuration. Warm regards, Peter. ... View more

Conceptually, the core construct that AppDynamics monitors is event based communication, where the processing of each message is one Business Transaction. Being stream based, rather than message based,  raw web sockets do not fit well into this model.  If your application operates a higher level message-based protocol over websockets where a complete message is sent over the socket and received, processed and replied to on the server, then the server side activity should be modelled as a Business Transaction, and will be tracked as such by AppDynamics. Business Transactions must start from an entry point the agent knows about.  The agents automatically detect some entry-points by virtue of the transaction logic being placed in a well-known container (e.g. within a servlet for java HTTP).  Business Transactions originating at points in code that are not known to the AppDynamics require custom configuration to be recognised (a POJO entry point, in the case of java, or using the agent API in the case of the Node.js agent). Backend activity (e.g. your external REST calls) will only be tracked if it is in the context of a Business Transaction (and made through a client that is either instrumented out of the box, or via configuration) To my knowledge, none of our agents support out of the box instrumentation for socket.io; a quick look suggests to me that is is event based, so if you were to instrument socker.emit() as an exit and socket.on() as a Business Transaction entry, I think you would see what you are expecting. If the messages are passing between server-side components and you additionally arrange for the AppDynamics correlation header to be passed in the message payload then AppDynamics would also show you the end to end correlation. I hope that explanation helps. Warm regards, Peter ... View more

Veerendra, The issue here is that the combination of tier name and node name are used by AppDynamics to uniquely identify one JVM. Thus, your configuration has told us there is one JVM, and that is what you see. If you give the 2 instances different tier names, or different node names, you will see both represented individually as you expect. For reference, take a look at https://docs.appdynamics.com/display/PRO45/Install+App+Server+Agents#InstallAppServerAgents-tier-node-namingTierandNodeNamingGuidelines Warm regards, Peter ... View more

Arun, It's good you have established that the basic proxy configuration works. What kind of proxy is it?  Does it simply allow access to any resource on the proxied host:port combination, or does it filter based on URL?  What do you see in the agent log if you  simply run java -javaagent:/<path-to-agent>/javaagent.jar -Dappdynamics.controller.hostName=<controller-host> -Dappdynamics.controller.port=<controller-port> -Dappdynamics.agent.applicationName=Test -Dappdynamics.agent.tierName=Test -Dappdynamics.agent.nodeName=Test –Dappdynamics.http.proxyHost=<proxy-host> –Dappdynamics.http.proxyPort=<proxy-port> -version Warm regards, Peter ... View more

Arun, The read timeouts that you highlighted in the log extract you posted indicate there is some issue preventing the agent communicating with the controller. There may be more specific messages earlier in the agent log, when the agent made the initial connection that should help you diagnose what is wrong. Can you successfully access the controller login page via your proxy using curl from the box where the agent is running?  Have you double-checked your proxy configuration, both at the proxy and on the agent side? Warm regards, Peter. ... View more

Bijal, You can stop the agent from collecting and reporting data as described here: https://docs.appdynamics.com/display/PRO45/Manage+App+Agents#ManageAppAgents-EnableandDisableAppAgents It goes without saying that the agent should not impact application performance, and if you find that it is you should work with support to figure out why. A common source of "agent overhead" arises from increased pressure on the garbage collector, in cases where the agent has been added to the process with insufficient headroom available in the heap. There is no way to totally detach the agent (uninstrumenting all the instrumented classes would obviously place more load on the JVM, so it's not clear that total removal of the agent would be a good move when under performance pressure) Warm regards, Peter ... View more

Bijal, What are you looking to achieve by stopping the agent? Warm regards, Peter ... View more

Mikel, Your post suggests that the CPU consumption does not seem to be correlated to load on the JVM, is that correct? Have you looked at the memory statistics?  When CPU runs away like this, excessive GC activity is often the cause. If that does not show any promise, you can use AppDynamics to collect some thread-dumps, which should give you an indication as to what is going on. Warm regards, Peter ... View more

Randy, You can elect to capture all SQL bind values if you like, as documented here: https://docs.appdynamics.com/display/PRO45/Call+Graph+Settings#CallGraphSettings-SQLCaptureSettings You need to take care if sensitive information is processed in your queries, for obvious reasons. Warm regards, Peter. ... View more

Maksym, We will need full agent logs to diagnose this.  To avoid posting these in the public forum, can you open a support ticket and attach them? Warm regards, Peter ... View more

Tracy, Since our agent is implemented in pure java, it is platform agnostic. You should follow the instructions for instrumenting WebLogic on Linux. Warm regards, Peter ... View more

I'm not clear what your issue is here.  Any single JVM can only have one agent within it. Can you provide more detail as to what is going on in your case? Warm regards, Peter. ... View more

Maria, I assume the TIBCO product in quesiton here is BusinessWorks, is that correct?  Can you tell me what version? I would expect a BT dashboard like this if the transactions had only been hit a small number of times.  The first time activity is seen, the BT registers and invocations subsequent to the registration will be collected and the statistics reflected in the BT dashboard. Is it possible that your system has only seen a small number of requests? Warm regards, Peter ... View more

Mikhail, Have you tried without the bootclasspath option?  In many cases that is not needed, as noted below the numbered steps in the documentation you linked. Warm regards, Peter ... View more

Good, I'm glad this is root-caused. ... View more

Does the app server start fine without the extra -D option for log4j.configurationFile? (other than the error message, which can be ignored) Warm regards, Peter ... View more