What is the current behavior with Dynatrace SaaS/Managed when the OneAgent encounters a process that is already being monitored by a "classic" AppMon agent (i.e. a Java Agent) which was configured manually?
I.e. will it recognize and report this fact accordingly and make it actionable in the sense that I am presented a warning along with the option to proceed with deep-monitoring the process by performing a restart which will then override the AppMon agent? Or will deep monitoring not be possible until the AppMon agent is removed from the application deployment by other means?
Answer by Michael L. ·
The OneAgent will add its deep monitoring into the Java process, and seeing as there cannot be both an AppMon agent and a OneAgent in a single process, the AppMon agent will not be included. There is no error produced (except for the fact that you won't be able to see it anymore in AppMon).
Answer by Joseph H. ·
The discovery happens after initially installing the OneAgent on a given host. At that point the Java process is discovered but not injected yet. This is where the JVM restart is required and if restarted the Dynatrace OneAgent would be injected and replace the existing AppMon Java agent. To avoid this replacement event, simply go into Dynatrace, and disable Deep injection for that process, or disable all Java deep injection on that host.
This approach allows for a clean upgrade path so the customer can transition to the Dynatrace Java agent at a convenient time of their choosing.
Answer by Joseph H. ·
Enrico, You can disable auto-injection at the host, process, process-group level. So for example if you had a bunch of containers and you didn't want to inject the Java agent into the JVMs on those containers you could modify the Process Group and set the "Automatically monitor newly found processes" switch to OFF.
But I start to wonder why you're adding OneAgent to containers which are already using AppMon Agents. It seems you should decide which product (AppMon or Dynatrace) you're going to use and not try to mix them.
Answer by Enrico F. ·
It seems that starting with managed version 172 the automatic disabling/overriding of configured AppMon Java agents no longer works and the result is that any configured AppMon agent (via agentpath VM option) will be injected together with Dynatrace's Java technology agent... which I assume can have all kinds of ugly sideffects....
This clearly wasn't the case with 170 so I assume there was a (silent?) change going from managed cluster version 170 to 172 - can anyone confirm this?
On our side we are currently observing Java processes being monitored with both solutions simultanously now... interestingly this has been without any functional impact so far....