Network Automation Software We are currently migrating this forum
over to our HelpSystems domain. Please
post all new threads in our new
HelpSystems Community Portal.
Post to the HelpSystems Forum
You are not currently logged on. You must be logged on in order to post. Log on
Or Create a new account
AutoMate Discussion
Decrease font size
Increase font size
Topic Title: Workflow Monitoring
Topic Summary:
Created On: 08/03/2012 06:14 AM
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
View similar topics View similar topics
View topic in raw text format. Print this topic.
Answer This question was answered by MatthewKoch, on Thursday, August 30, 2012 5:53 AM

Answer:
Thanks Leonard,

I will give this approach a shot.

--Matt
 08/03/2012 06:14 AM
User is offline View Users Profile Print this message

Author Icon
MatthewKoch
Apprentice (20-49)

Posts: 26
Joined: 12/19/2011

Hello all,

I am attempting to set up a structure where I can monitor our critical nightly jobs and log the results. I have several separate workflows (each on their own schedule) that perform various tasks. Is there a way I can set up a "parent" workflow that will treat these workflows as children and send an e-mail if one or more of them fail, or would I need to re-engineer the way my workflows are constructed?

Any advice is welcome.

Thanks,
Matt

 Category Survey
 08/03/2012 01:50 PM
User is offline View Users Profile Print this message

Author Icon
Leonard Amabile
HelpSystems

Posts: 5454
Joined: 05/15/2007

Hi Matt,

In order for this scenario to work properly, you will need to move the schedule trigger objects from the subworkflows and add them into the parent workflow, each pointing to the appropriate subworkflows. You can then have all of the subworkflows either share the same failure structure or build them independent in the parent workflow.









 Category Survey


-------------------------

Leonard Amabile | Director, Cross Platform Support
AutoMate | InterMapper | Skybot | Divisions of HelpSystems
T: +1.213.738.1700 | F: +1.213.738.7665
 08/07/2012 08:04 AM
User is offline View Users Profile Print this message

Author Icon
MatthewKoch
Apprentice (20-49)

Posts: 26
Joined: 12/19/2011

Leonard,

Thanks for the information. I've followed your advice and I've set up a parent workflow that contains each child workflow I want to get the results of. Each child workflow points to a "Results" task (on success OR failure) that I want to use to compile information about each. The end goal is to have a file that shows me each workflow in the dependency flow from start to finish and note success or failure.

If you could take a look at the attached screenshot, you can see how I have it set up currently. Does this make sense to you? Would you approach this in a different way?

So far, I've been unable to come up with an expression that will grab the name and result of the completed workflows in order to create a text file with the results.


 Category Survey


Click for full image
Click for larger image



Edited: 08/07/2012 at 08:13 AM by MatthewKoch
 08/11/2012 10:21 AM
User is offline View Users Profile Print this message

Author Icon
Leonard Amabile
HelpSystems

Posts: 5454
Joined: 05/15/2007

Hi Matthew,

If the sub workflows are not dependent on the previous one completing first, then I would recommend removing the success arrows between each sub workflow and instead adding 3 independent schedule triggers within the parent workflow pointing to each sub workflow. This will allow your reporting to be more specific to what workflow succeeded or failed.



 Category Survey


-------------------------

Leonard Amabile | Director, Cross Platform Support
AutoMate | InterMapper | Skybot | Divisions of HelpSystems
T: +1.213.738.1700 | F: +1.213.738.7665
 08/13/2012 07:54 AM
User is offline View Users Profile Print this message

Author Icon
MatthewKoch
Apprentice (20-49)

Posts: 26
Joined: 12/19/2011

Leonard,

What I am attempting to do is introduce some dependencies so that when the nightly workflows start, each one is dependent on the previous one completing successfully. The end goal would be to have a summary of which workflows did and did not complete.

Suppose I have workflows A, B, C and D as part of my "Critical Processes." Currently they are all separate workflows with separate schedules. The logic I am trying to introduce is to have one schedule kick off workflow A, and the flow would be A --> B --> C --> D. If for some reason A fails, I would want a log saying that A failed and as a result, B, C and D were not executed. If B fails, I would want a log saying that A completed, B failed, and as a result C and D were not executed.

I hope this makes sense. What would be your recommendation in a situation like this?

 Category Survey
 08/13/2012 03:22 PM
User is offline View Users Profile Print this message

Author Icon
Leonard Amabile
HelpSystems

Posts: 5454
Joined: 05/15/2007

Hi Matthew,

Your scenario, as outlined, would be our recommendation as well.




 Category Survey


-------------------------

Leonard Amabile | Director, Cross Platform Support
AutoMate | InterMapper | Skybot | Divisions of HelpSystems
T: +1.213.738.1700 | F: +1.213.738.7665
 08/30/2012 05:53 AM
User is offline View Users Profile Print this message

Author Icon
MatthewKoch
Apprentice (20-49)

Posts: 26
Joined: 12/19/2011

Answer Answer
Thanks Leonard,

I will give this approach a shot.

--Matt

 Category Survey
Statistics
18258 users are registered to the AutoMate Discussion forum.
There are currently 0 users logged in.
The most users ever online was 5551 on 01/08/2018 at 11:11 AM.
There are currently 2032 guests browsing this forum, which makes a total of 2032 users using this forum.

FuseTalk Enterprise Edition v4.0 - © 1999-2020 FuseTalk Inc. All rights reserved.

Sitemap Network Automation Software Blog