Im having a difficult time creating a email alerts specifically for Time-Outs. I'm not sure what 'Event Trigger' to use that will specifically alert on Time Out issues. Anyone have any ideas?
Details: Using Tidal 6.2.1, When A job or job group time's out, I want to send a email alert. I already have alerts for things completing abnormally and also running longer than expected.
Thank you for the very quick reply. I thought about using the "Job not ready by end of its time window". event trigger but I don't think that is going to work. See below:
I have a job stream that runs from 6am - 12am
In the job stream is a PeopleSoft Job
The peopleSoft job recently timed out because it could not connect to the SAN and the Peoplesoft job timed out only. other jobs did not time out
So the stream is still running but the PeopleSoft job is in timeout status and the stream was still within its time window.
I wanted to alert specifically when there is a timeout even though the stream is within its timeout window. Thoughts?
Yes I could use 'scan abnormal string' but we use the Exit Code for just about all the jobs. by using the 'scan abnormal string', i would have to adjust 90% my jobs to use the abnormal string to catch that.
I do appreciate the feedback but not sure that would work. I haven't found a good answer to this dilemma yet. We currently use 'eyeball' technology to catch those ;).
Okay, we don't want you making radical changes to output strings if you're reliant on them for normal processing.
The "Job Stopped" trigger isn't working. I have to assume that the triggers of "Job Running Longer Than Its Maximum Time", and "Job Running Past Time Window" have both been considered and weren't working either. Which is frustrating. Either a job runs past its expected time, or it's stopped. Has to be one of the two, but apparently not.
You could always replace the eyeballs with another job. Create something which is timed to run at the point where your hanging job is supposed to have ended. It will have a dependency on the hanging job which triggers on a status of Completed Normally, but uses the <> Operator.
I hope 6.2 uses the Operators on job dependencies. It's been long enough since I've last used that version that I don't remember. I'm also having trouble coming up with a complete Users Guide which lists all of the Job Dependency options.
The monitoring job will launch and then squawk if the hanging job has not completed normally by then. It's a clumsy solution which will result in duplicate emails if the hanging job has decided to Complete Abnormally instead of going to Timed Out. It would also require that you create a similar monitoring job for each hanging job with this problem.
Does 6.2 allow for both Job Events and Group's Events on parent job groups? You could try adding an event on that level using the "Triggered After Job's Own Events" option. If something about the Timed Out status is interfering with the hanging job's events, applying "Job Stopped", "Job Running Past Time Window", or "Job Running Longer Than Maximum Time" might recognize those conditions from the Group level.
Note that a parent's Job Events applies to just that parent Job Group. A parent's "Group's Events" applies to each job contained within that job group. It's in the Group's Events where you can set an event to trigger before or after a job's own event.