- Set the debug flag "com.dynatrace.diagnostics.dumpClasses" to true on the collector that the agent in question reports to.
See here: Setting AppMon Collector Debug Flags for an introduction on how to set debug flags for a collector
- Restart the collector
- Restart the application in question (with AppMon agent injected)
- This should result in the creation of a folder called "
<DT_HOME>/collector/cache/out" for a Java or "
<DT_HOME>/collector/cache/modules" and "
<DT_HOME>/collector/cache/transformed" for a .NET application. These folders contain the original and transformed byte code of the classes that get loaded in the application. These files may exist on the file system of any Collector in your Collector Group. Check the file systems of all, or determine what Collector the Agent is currently connected to. Please verify that these folders are present, and if not, repeat steps 1 - 3. If they still do not show up, contact support.
- Now reproduce the bug that happens when AppMon agent is injected.
- Recursively zip the "
<DT_HOME>/collector/cache/out" (Java) or "
<DT_HOME>/collector/cache/modules" (.NET) folder and send it to support for analysis.
- Disable the debug flag again by setting its value to "false".