Hi David,
If this it, then sure it can be used as Mule runtime runs on JVM. Everything that runs on JVM can be used with inspectIT. Setup is quite simple, alter the [mule]/conf/wrapper.conf and add following:
# inspectIT settings
#wrapper.java.additional.<n>=-javaagent:[path-to]/inspectit-agent.jar
#wrapper.java.additional.<n>=-Dinspectit.repository=localhost:9070
If you want to start Mule with inspectIT un-comment the settings and replace the <n> with proper numbers based on the additional options that you specified until now. For me this looks like:
...
# GC settings
wrapper.java.additional.9=-XX:+HeapDumpOnOutOfMemoryError
wrapper.java.additional.10=-XX:+AlwaysPreTouch
wrapper.java.additional.11=-XX:+UseParNewGC
wrapper.java.additional.12=-XX:NewSize=512m
wrapper.java.additional.13=-XX:MaxNewSize=512m
wrapper.java.additional.14=-XX:MaxTenuringThreshold=8
wrapper.java.additional.15=-Dorg.quartz.scheduler.skipUpdateCheck=true
# inspectIT settings
wrapper.java.additional.16=-javaagent:/home/ise/agent-link/inspectit-agent.jar
wrapper.java.additional.17=-Dinspectit.repository=localhost:9070
as 15 was the last used index before adding inspectIT settings.
I'll add this to the documentation as well.
Cheers,
Ivan