I wanted to use inspectIT to find why my web application was slow and I finally realize I couldn't for 2 main reasons:
In order to see where the JVM passed its time handling one specific request, I must declare in a Profile Configuration all the classes I want to "watch" in order to be later analyzed in the "Invocation Sequence" tool. But then, as I don't know where the contention points are, I want to declare all the classes of my application in an HTTP & Timer Sensor definitions in my new profile, using "mypackage.*" notation for class name.
If I activate this new profile and restart my Tomcat server, it will never stop (or is so slow for starting that I killed it after having waited for more than 2 hours, hanged at "rocks.inspectit.agent.java.javaagent.JavaAgent premain" log line)
That's 3 years since I developed a tool that was using a stacktrace sampling mechanism in order to handle that use case ( http://webapp-watcher.com/overview.html ), would it be possible for the agent to be configured in a sampling way (that is to say without having to instrumentalize the classes), so that we can later on analyze where the JVM passed its time without knowing where to look before launching the application (so before launching the agent)?