False flag's for SLAs with AE job's using file triggers

Products

• iDash Workload Automation

Issue/Introduction

We have multiple SLAs flagging as predicted miss, but showing as MET/completed in idash table view and autopsy. Could these false flags be related to the fact that autosys jobs are triggered by a dummy BOX job which is triggered by a file transfer outside of autosys? If so, would turning off the predicted miss and only using at risk and miss alerts be more effective?

Environment

Release : 12.1

Component :iDash for AE

Resolution

The AE jobs being run by file triggers will be a problem for iDash. We only do forecast from history for CA 7 jobs, not for AE jobs so iDash will not be able to forecast those jobs. We will likely show predicted miss until they actually begin to run. The dynamic SLAs feature we have coming up in the next release will be able to deal with flows like this. The SLA would not be monitored until the file transfer job came in, so it would skip the predicted miss portion you're dealing with now. For now, the only thing you can do is adjust the start tracking window so that the SLA doesn't enter monitoring until some time after the job in question is usually run.