Discussion Feed

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

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