Identifying Long Running Jobs

paranoid · Post by **paranoid** » Wed Aug 26, 2009 2:04 pm

Hi,

Is there any one to identify long running jobs or run-time of the DS jobs using a command or using DS Administrator?

That would really help me out!!

Thanks

Sue

ray.wurlod · Post by **ray.wurlod** » Wed Aug 26, 2009 3:30 pm

You use Director for this. Status is Running (you can filter this) and sort by start time.

kduke · Post by **kduke** » Wed Aug 26, 2009 4:17 pm

Start storing job run time information with EtlStats. It is free.

paranoid · Post by **paranoid** » Fri Aug 28, 2009 12:54 pm

Ray,

I have been doing that in director whenever i need to check the status of a particular job manually. I am looing for something that can be automated.

Duke, I will try ETL STATS and update this post.

Thanks

Sue

chulett · Post by **chulett** » Fri Aug 28, 2009 1:06 pm

Are you looking to do this identification after the fact or as the jobs are running? Regardless, trying to determine how long is 'too long' is not always a simple task.

paranoid · Post by **paranoid** » Sat Aug 29, 2009 11:42 am

Chulett,

I would to like to do this identification after the fact immediately after every load on a day-to-day basis so that i can collect the statistics for few days and observe the performance of the job.

Thanks

Sue

chulett · Post by **chulett** » Sat Aug 29, 2009 2:27 pm

OK, for the 'collect the stats after each job run' approach, ETLStats gives you a huge leg-up there.

tagnihotri · Post by **tagnihotri** » Mon Aug 31, 2009 10:44 pm

The way I have achieved this is, by writing the start time of each job at the start of job and then keep on checking the elapsed time from this log file and if a job is running more than expected*, an alert is raised. Also, I am currently running the jobs using UNIX scripts, but then the initial implementation was done using before and after job routines.

*Have stored the average time or acceptable wait time for each job in another file, which can then act as the acceptable time limit for comparison.

kduke · Post by **kduke** » Tue Sep 01, 2009 1:45 am

EtlStats can get all the jobs stats for the last time a job was run. When it asks for job name then just put all in there and it will get every job's last run. It stores elapsed time in a table, so it is easy to sort by this. If you run daily then just get all the job runs the next morning.