Adrien, Firstly, what agent version are you using?  Support for Vert.X 3.5 was added in the most recent release (4.5) which came out last week so you will need to use the 4.5 agent. If you are already running v4.5 of the agent (or if you try that and see no change) then can you try downgrading to Vert.X 3.5.0, and see if that helps? If not, can you describe how the application works; what is processing the incoming HTTP requests, the Vert.X HTTP server or some lightbend HTTP server (e.g. Akka HTTP, etc.) Warm regards, Peter ... View more

Auto discovery for transactions originating in the netty 4 web server is a backlog item currently. In the short term, you are best off working with support to identify a configuration that works for your environment. Warm regards, Peter ... View more

Benjamin, WebSphere Liberty edition is currently not a certified platform. If you look in the agent logs, you will see either permission or classloader errors relating to JMX access. In other respects, the agent should function normally. Warm regards, Peter ... View more

Ashok, Your first step will be to introduce the AppDynamics java agent into the JVM running your Spring Boot application. This process is described here. Warm regards, Peter ... View more

Activity is only shown on the flowmap if an entry point is hit.  Since you describe your process as a standalone background process, I think it's very likely that none of the entry points configured out of the box are present. You will need to configure a custom POJO entry point. ... View more

Pankaj, How are you deploying your application?  How are you trying to inject the agent?  Do you have a copy of the agent logs? Warm regards, Peter ... View more

Version 4.3.x of the agent was where we introduced support for java 8   You will need to use v4.3 or higher of the agent to instrument any java 8 JVM Actually, I take that back; 4.2 did include java 8 support.  What happens when WebLogic fails to start?  Do you get any error output? Please note, however, v4.2 of the product has now reached its end of life. Warm regards, Peter ... View more

Can you share the contents of the /var/log/eb-activity.log file? Thanks, Peter ... View more

I suspect your issue is with the curl command.  This is a working EB config that adds the agent to tomcat files: "/tmp/appagent.zip": mode: "000444" owner: ec2-user group: ec2-user source: https://packages.appdynamics.com/java/4.4.0.3/AppServerAgent-4.4.0.3.zip # command are executed in alphabetical order commands: 01reset: command: "rm -rf /opt/AppDynamics/appagent" ignoreErrors: true 02makedir: command: "mkdir -p /opt/AppDynamics/appagent" 03unzip: command: "unzip /tmp/appagent.zip" cwd: /opt/AppDynamics/appagent 04perms: command: "chown -R tomcat:tomcat appagent" cwd: /opt/AppDynamics 05cleanup: command: "rm /tmp/appagent.zip" option_settings: - option_name: appdynamics.controller.hostName value: <CONTROLLER_HOST> - option_name: appdynamics.controller.port value: <CONTROLLER_PORT> - option_name: appdynamics.controller.ssl.enabled value: <true/false> - option_name: appdynamics.agent.accountName value: <ACCOUNT_NAME> - option_name: appdynamics.agent.accountAccessKey value: <ACCESS_KEY> - option_name: appdynamics.agent.applicationName value: <APPLICATION_NAME> - option_name: appdynamics.agent.tierName value: <TIER_NAME> - option_name: appdynamics.agent.nodeName value: <NODE_NAME> - namespace: aws:elasticbeanstalk:container:tomcat:jvmoptions option_name: JVM Options value: -javaagent:/opt/AppDynamics/appagent/javaagent.jar I hope this helps. Warm regards, Peter ... View more

Erwin, I don't see your agent logs on the thread.  Without the full logs, it's impossible to diagnose. Could you post them? Warm regards, Peter ... View more

Ah, OK.  That validates that the collector is getting called, which is what I wanted to confirm. I think the problem you're running in to is that the getter chain wants to get the data value as a string, and since your method returns an un-boxed int, it can't do the necessary type conversion. It should work if you change your method to return the length as a String, or an an Integer (which has a toString method that could be used to yield a string result) Warm regards, Peter ... View more

So when during the BT execution is your init method called?  Can you provide a snippet of the application code that shows the context of that call? Warm regards, Peter ... View more

Moco, You need to define a data collector on a method that is called as part of the processing of the BT. That data collector can access methods on any of: the object instance on which the instrumented method is run the object(s) passed to the instrumented method as parameters the object returned from the instrumented method The key here is that a data collector is passive - it needs to be placed on a method that will be run in the course of the processing of the BT in order that it can step in and collect the data you need. Warm regards, Peter ... View more

Simon, Just to update the community for posterity (thanks for the prompt Simon) the solution was to upgrade to v4.3.2+ of the agent which introduced out of the box configuration for v3.0 and above of the Vert.x framework. Additionally, please note that v3.5 of Vert.x introduced changes within the framework, meaning that v3,5+ of Vert.x is supported by out of the box configuration in v4.4.3+ of the agent. Warm regards, Peter ... View more

A JVM crash is always a result of a JVM bug (unless it is triggered by an issue in native code accessed through JNI.  The AppDynamics agent contains no native code) .  Of course, adding an agent to the JVM changes what is going on within the JVM (for instance, classes getting retransformed would not happen with no agent present) which can cause JVM bugs to be triggered which are not triggered in the absence of the agent. Unfortunately, selecting g1gc seems to uncover more bugs of this nature than you might hope (often, coincident with class retransformations) You need to see if the crash backtrace corresponds to a known JVM bug and if so, upgrade to a JVM where it is fixed.  Or select a different GC algorithm.  Or, you can disable dynamic class retransformations which does seem to avoid many of these issues (at the expense of not being able to change instrumentation on the fly) Warm regards, Peter ... View more

Although I have not personally been involved, we have customers who are doing this so I do know it works. (we also have customers instumenting JVMs on zOS too) Warm regards, Peter ... View more

Excellent!  I'm glad you're off and running! If you wish to automate download of the AppDynamics software in the future, the steps to do so are documented here: https://docs.appdynamics.com/display/PRO44/Download+AppDynamics+Software Warm regards, Peter ... View more

It looks as if the agent cannot contact the controller. Can you zip up and attach all the files under the logs and conf directories beneath the versioned agent directory within you agent installation (which will have a name of the form ver4.x.y.z, where x y and z are the version numbers) Then we can try and see what the connectivity issue is. Warm regards, Peter ... View more

Can you post the first 20 or so lines of your platform-setup-x64-linux.sh script please? From this error message, I am not sure if this has the expected content. ... View more

You are correct that you need to add the -javaagent option to your JBoss start script. I am not sure if you have reviewed the instructions in the documentation which describes how to do this for JBoss; if so, does it raise any specific questions? In terms of connecting the agent to the controller, you need to provide a controller-host and contoller-port setting that is used by the agent to locate the controller.  If these point to a remote controller, that is what the agent will connect to. controller host and controller port can be set in the agent's controller-info.xml file, or as system properties on the JVM command line, as described in the general agent configuration documentation. I hope this information helps. Warm regards, Peter ... View more

You can monitor akka appications with AppDynamics, but the built-in configuration that tracks thread hand offs, entries and exits is quite sensitive to the precise version of the framework in use. What agent version are you using, and what akka version? ... View more