Data360 Analyze

Hi,

I'm exploring the possibility of having some sort of master switch which will act as general trigger for all flows. Use case: Hundreds of flows are scheduled and due to the instability or some problems with ETL at the source some of flows fail to run. Having master switch would act on possible different triggers: email or some other form of alert from IT or DBA and will delay running all flows and run them after 'green' alert' or after x hours. Integrating meta checks in every flow is possible, but it's a long task due to the number of flows. Therefore having umbrella/parent switch will be more efficient and robust. Anybody have come across or have implemented solution like this before? 

Thanks,

IC

------------------------------
Irakli Chitishvili
Data Trust Associates
------------------------------

Have you considered having a master dataflow and using the "Execute Data Flow" node?

For example we have some scenarios where we pole a DB waiting for an update before triggering the next step which would be the dataflow. This has also been implemented by looking at a sharepoint site and waiting for a file to land, again this is based on a pole.

------------------------------
Toby Harkin
Telstra Corporation Limited
Sydney NSW

Original Message:
Sent: 09-26-2023 03:48
From: Irakli Chitishvili
Subject: Master Switch/Trigger Feature

Hi,

I'm exploring the possibility of having some sort of master switch which will act as general trigger for all flows. Use case: Hundreds of flows are scheduled and due to the instability or some problems with ETL at the source some of flows fail to run. Having master switch would act on possible different triggers: email or some other form of alert from IT or DBA and will delay running all flows and run them after 'green' alert' or after x hours. Integrating meta checks in every flow is possible, but it's a long task due to the number of flows. Therefore having umbrella/parent switch will be more efficient and robust. Anybody have come across or have implemented solution like this before? 

Thanks,

IC

------------------------------
Irakli Chitishvili
Data Trust Associates
------------------------------

Hi,

I'm exploring the possibility of having some sort of master switch which will act as general trigger for all flows. Use case: Hundreds of flows are scheduled and due to the instability or some problems with ETL at the source some of flows fail to run. Having master switch would act on possible different triggers: email or some other form of alert from IT or DBA and will delay running all flows and run them after 'green' alert' or after x hours. Integrating meta checks in every flow is possible, but it's a long task due to the number of flows. Therefore having umbrella/parent switch will be more efficient and robust. Anybody have come across or have implemented solution like this before? 

Thanks,

IC

------------------------------
Irakli Chitishvili
Data Trust Associates
------------------------------

Toby's suggestion to use a parent data flow containing some logic and the Execute Data Flow node is a good solution if you want to be able to specify a range of prerequisites that need to be satisfied before running a child data flow. The logic in the parent data flow could, for instance, check the status of services in a DB table that is updated by IT or a trigger from other monitoring software. If all checks are passed the Execute Data Flow node then runs the child data flow. Note, the schedule would be provisioned on the parent data flow not the child.

If you want to have a mechanism that provided coarse control to enable/disable all schedules then you could use an external system to leverage the AnalyzeCli tool to pause/resume the scheduler.

------------------------------
Adrian Williams
Precisely Software Inc.

Original Message:
Sent: 09-26-2023 03:48
From: Irakli Chitishvili
Subject: Master Switch/Trigger Feature

Hi,

I'm exploring the possibility of having some sort of master switch which will act as general trigger for all flows. Use case: Hundreds of flows are scheduled and due to the instability or some problems with ETL at the source some of flows fail to run. Having master switch would act on possible different triggers: email or some other form of alert from IT or DBA and will delay running all flows and run them after 'green' alert' or after x hours. Integrating meta checks in every flow is possible, but it's a long task due to the number of flows. Therefore having umbrella/parent switch will be more efficient and robust. Anybody have come across or have implemented solution like this before? 

Thanks,

IC

------------------------------
Irakli Chitishvili
Data Trust Associates
------------------------------