ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Exceed SLA Alert not received on Tidal jobstream when jobstream only as shot running non group jobs

book

Article ID: 239033

calendar_today

Updated On:

Products

Automic Automation Intelligence

Issue/Introduction

Exceed SLA Alert not received on Tidal jobstream when jobstream only as shot running non group jobs.

 

Environment

Release : 6.4.2-1

Component : AUTOMIC AUTOMATION INTELLIGENCE INTEGRATION FOR TIDAL

Resolution

In a jobstream that has only one or two non Tidal Group Jobs, where the group job starts long before the non group jobs, and the non group jobs completed very quickly, it is possible AAI may not generate an exceeded SLA alert.

 

If you set the AlertGenerator logger to DEBUG, you can usually search the jaws.log for jobstream name to see when AAI is checking for alerts on a jobstream.

In this scenario you may not see the jobstream in the DEBUG logging.

Tidal Group jobs, even when set to allow to start a jobstream run, appear to not trigger the Alert activation where AAI will monitor a jobstream for alerts thresholds being breached.

 

Defect DE499785 has been raised for this and is under investigation.