Automic Workload Automation

Hello Experts,

Is there any option to monitor delay in start time of jobs in AWA  ?

For example if I have a job scheduled to run at 10 AM and if the job is not started in specified time interval, say within 15 mins of scheduled start time, an alert should be triggered.

Is there any option in AWA which can be used to monitor it ?

Or any other customized solutions ?

Regards,

Abin

Hi Abin,

You can create a call alert/notification and configure it under Time checkpoint section on General tab of the job. 

I have been using it and it works fine.

Regards,

Shashank

Hello Shashank,

I have gone through the General tab, but could see only options to set monitoring enabled for minimum and maximum run time for jobs.

But I couldn't find any option to enable monitoring for delayed start. Can you please explain bit more about achieving it using below options ? 

.

Regards,

Abin

You will get that in general tab of task properties of the job. See below.

Thanks,

Shashank

Thanks Shashank. But I can see this option only with Workflows.

But our requirement is to set this up at job level or scheduler level.

Regards,

Abin

If the job has been configured and scheduled in a scheduler at a particular time it will trigger at that time. You should not be required to set up additional monitoring or alerts for it. If it has pre-conditions or syncs, it is better to configure the job in a workflow and have alerts set up.

Thanks,

Shashank

Hi Albin, 

you can also use the SLO objects for that use case. Using these object, you can also get nice reporting on how often this happened. 

Best regards,

Robert

Hello Robert,

Can you please provide some more information on using SLO for monitoring delayed start time of job ?

Regards,

Abin

The SLO feature is new with V12.  We are still on V11.

A solution we like to use is to build a new workflow that is scheduled to run at 10:15 with a single email task.  The email task has a precondition "CHECK HISTORY" rule that checks the state of the 10:00 event.  It then decides to either run or skip the email task based upon what the precondition rule detects.

I've played with the SLO feature at a CA-World class, and I thought it was less flexible than this technique.  The custom workflow can be engineered to do any behaviors you want it to do.

Hello Pete,

Thank you for your inputs. I saw the option to set Pre condition in  a workflow with an email object.

But can you please provide some more information on how we can set it up to monitor the delayed start of individual jobs using 'CHECK_HISTORY' ?

I am very much new to Automic and not familiar with all these options.

Regards,

Abin

In our case, it has been sufficient to check and make sure the process ended in a timely fashion.  I've included a sample.  I don't see an option for checking the start of a process though.   One would have to do some scripting for that type of test, and I don't have any examples of that requirement.   It would probably require the use of the GET_UC_OBJECT_STATUS() script function.