we had an already existing Dynatrace enabled mule environments.
A reboot of mule linux servers happened due to an issue upon which we see Dynatrace stopped monitoring the mule processes. We see naming rules are not able to detect as multiple jetty processes instead it shows up as a compressed single java process with a class name showing up as "org.mule.module.reboot.MuleContainerBootstrap"
Did anyone had similar issue, any idea how to fix this.
Solved! Go to Solution.
Hi @SOWJANYA P.
Please contact support about your inquiry. This might be
caused by multiple reasons and we need to take a closer look.
You can create a
support ticket here: https://support.dynatrace.com/supportportal/secure...