Is there a way to have dynatrace monitor tasks kicked off by quartz
One of our applications runs with quartz embedded inside of the tomcat, and it appears that dynatrace is not monitoring any of the activity started by the scheduler. Is there any way to make this happen?
Jonathan,
Check to see if the thread start method you can see in your abbreviated PurePath is included in the OOTB Thread Start Tagging sensor pack.
You might have to escalate this to the lab.
-- Graeme
Hi,
Did anyone work out the best methods to instrument for Quartz? I am currently on a customer site and they have Quartz. I tried starting a PurePath from the method Roman suggested above but it gives me a completely separate PurePath with only that method plus a thread start method.
Thanks,
Richard (guys) how do you add such a Monitor in dynaTrace that it create a new Pure Path?
Using Roman's suggestion above, I would place a sensor on Job.execute() and set it to "Active and Start PurePaths"
For more information on sensors in general as well as what we call "entry points" check out the documentation: Sensor Configuration
Many thanks. It worked. Do you have an idea how I create a Application Mapping for it? No this pure paths are simply in the Default Application, but I would like to move it into a specific one.
It has no URI/ URL of course but it seems that "AppId" works too which is created by the ADK (what ever that is). Not sure where I can see the APP ID of this Pure Path.
Hi Paul,
There is a popular request for enhancement around what you are looking for. It looks like it will be implemented in the Spring 2014 release but an "up vote" and a comment shouldn't hurt 
Reading through some Quartz docs the Job.execute method might be a good, generic entry point. Try putting a sensor on that method and make sure it is active and can start PurePaths.
package org.quartz;
public interface Job {
public void execute(JobExecutionContext context)
throws JobExecutionException;
}
http://www.quartzscheduler.org/quartz/tutorial.html#jobsNTriggers
Best, Roman
Hopefully someone can give you a more experienced answer, but without knowing anything about the application:
You can run a CPU sample during a task run and follow the thread you see running the task to a good entry point. I typically go one or two levels below the run() method. Keep in mind that the default view of a CPU sample is a reverse call tree
I'm capturing a purepath that's kicked off by Quartz scheduler using the method Richard described above. After you take the CPU sample you can filter view by thread and place a sensor on the method that you want to start a purepath. Make sure you allow that method to start a purepath or you won't see anything.
