Tidal jobstream Generates Exceeded SLA hours after Late time

Products

• Automation Analytics & Intelligence

Issue/Introduction

Tidal jobstream generated Exceeded SLA alert hours after Late time.

 

Alert is triggered just after the Target Job ran.

Environment

Release : 6.4.2-2

Component : AUTOMIC AUTOMATION INTELLIGENCE INTEGRATION FOR TIDAL

Resolution

For this particular  tidal jobstream, we found the target job, ran normally multiple times, one of those times it generated an alert. 

 

 

 

When the job ran one of the times it was already after the late time and immediately generated an alert.

 

This can occur with a jobstream that has a User Defined Late Time will not work well with a job that runs multiple times per day some times.

 

A duration based late time would work better when a target job runs more then once per day.