Add job start time to Board logs

Laurie Thompson

1) What is your idea?  To have the ability to track the start time of procedures and data readers (Board jobs) so any jobs that run for longer than a certain amount of time can be identified and someone alerted to investigate whether the job has become stuck or is hanging.

2) What specific problem are you trying to resolve?  The start time of procedures and data readers in Board is missing from logs.

If a Board job (data reader or procedure) started at 02:00:06 AM and it’s still running after 5 hours, it is likely that it is stuck, or hanging. The idea would be to track or monitor the runtime of jobs in order to alert a support team to log into Board to check running processes and deal appropriately with any jobs that are stuck or hanging.

3) What workaround have you found or used?  At the moment, only when developers or system users are impacted by an issue or bug does anyone get alerted to the fact there may be stuck jobs.  Someone then looks at the LMA or Board running processes to see if there are any stuck jobs.

This is not an acceptable option for a live production system used by paying customers.

4) What is your role in the organisation?  I am the Programme Manager for my organisation's Data Programme.  We are developing data services for paying customers.