John, Is your Kotlin code on the server side, or in a mobile application? So far, we have had almost no asks for kotlin support on the server side, so we have not investigated what out-of-the-box configuration the language and its frameworks might need. That said, like other JVM-based languages, it should work, given appropriate configuration of custom entry points and the like. Warm regards, Peter ... View more

Ronald, The JVM originating from Sun/Oracle/OpenJDK allows agent to re-write application bytecode on the fly with no significant performance penalty, meaning that the agent can dynamically change instrumentation at runtime when necessary. The J9 JVM from IBM allows the same capability, but even requesting it disables certain runtime code optimisations that the JVM can make, meaning that the CPU cost per unit of work in the J9 JVM is higher if this ability is enabled. The only difference between our 2 flavours of java agent is that the "IBM Java Agent" does not request the ability to retransform classes at runtime, so as not to force applications to incur this performance penalty.  (Obviously, this has the downside that it cannot change instrumentation on the fly) The above is entirely independent of what applications / frameworks you are running, so you should choose the agent based on whether the JVM is J9 or the HotSpot one. Warm regards, Peter ... View more

Murthy, The agent does not currently support java 11 (planned for the next monthly release) If you look in the agent log, you will likley see some exceptions. You should find that everything works well with a prior JVM release. Warm regards, Peter ... View more

Patrick, By itself the machine agent will not touch any logs other than its own.  It is almost certain that someone has configured a machine agent extension of some kind which is opening the logs. I am afraid your only course of action is to track down whoever set up the machine agent and work with them. Warm regards, Peter ... View more

Yes, the java agent is not OS dependent, so WebSphere 7 running on AIX is supported. It sounds as if you may have communication issues between your agent and the controller.  Do you see anthing in your agent log which may indicate the source of the problem? ... View more

From an AppDynamics perspective, the agent is fine with or without the presence of tomcat provided it gets the needed configuration. There is some documentation that talks about setting the agent up in a docker environment, which also points to the dockerfiles for some images we have created ourselves as examples. I hope this helps you arrive at the optimal configuration for your scenario. ... View more

If the agent is reporting, it posts a value of 1 to its Availability metric (shown below in the metric browser for a node called WEB1_NODE in the ECommerce-Services tier of the ECommerce application) You can build health rules and alert on this at the node level, to get notification when a node is not reporting, or a the tier level to ensure each tier always has a certain minimum number of nodes. so if you see a 1 posted in that metric, you know the agent reported. For your cases 1 and 3, this wil be 0. For case 2, it is extremely unlikely that this metric would be 1 and absolutely no other data would be reported from the agent.  That said, if it is 1 but you do not see Business Transaction activity that you expect within the instrumented node, then it is likely you are missing necessary entry points because your application is not running within a framework for which there is out of the box configuration. Warm regards, Peter ... View more

Brad, You need to mark the nodes as historical when they shutdown, using the agent property, or alternatively, there is a controller API you can call to mark nodes as historical. Once marked as historical, nodes are automatically purged Warm regards, Peter ... View more