BP production support notification procedures

[sivaprasadfeb14]

Hi All,

I came across a use case in Blue Prism where we are looking some thoughts on how to achieve. Assume there is a BOT scheduled to run every one hour such as 00:00 AM, 1:00 AM, 2:00 AM, 3:00 AM...etc., in case if BOT didn't run any one instance e.g: 2:00 AM, will there be any way to configure/build a process to notify Support team with instance details which didn't run.

FYI, there could be a various reason for not getting executed an instance such as BP Server went down , BOT may be offline etc.,

Thanks,
Siva

 

[wildCat]

Starting from blueprism v5, you can map the BP itself. Create a process, which will be checking the control room.

 

[sivaprasadfeb14]

Hello wildCat, Thanks for your time in replying to my query. If you don’t mind can you give some insight about creating Control Monitor process.

 

[VJR]

Hi All,

I came across a use case in Blue Prism where we are looking some thoughts on how to achieve. Assume there is a BOT scheduled to run every one hour such as 00:00 AM, 1:00 AM, 2:00 AM, 3:00 AM...etc., in case if BOT didn't run any one instance e.g: 2:00 AM, will there be any way to configure/build a process to notify Support team with instance details which didn't run.

FYI, there could be a various reason for not getting executed an instance such as BP Server went down , BOT may be offline etc.,

Thanks,
Siva

You can also make use of writing to a log file concept.
Refer Post #5 here.

The very first stage of every process could be writing to the log file with something like "Process XX started" along with some details from the Calc stage Environment functions like Server name, Resource etc. Set the script file to run in the Windows Scheduler at 5 minutes after your above mentioned times (eg; 00:05 AM, 1:05 AM etc). From the script file read the latest message in the log file and if the message does not have "Process started" or is empty then shoot an email to your Support team indicating that Process XX did not start. Writing a line of text to a text file doesn't involve any configuration, only the Append to file action with the correct folder path. A new text file with the current date-time stamp can be generated on each run or may be you can append an earlier file in which case anyways the actual log message is going to contain the current date-time stamp.

Instead of the script file you can also have a Blue Prism process do this checking and email sending, but there are caveats like what if this BP process itself had problems in starting, and things like you need to have a free resource to run this process etc.

Another option is to have the first stage of the process to send an email to the Support team that the process has started. But again, this stage could fail while sending the email. In this case the On Support team should be made aware that if an email is not received within 5 minutes of 12 AM, 1 AM... then it could mean that the process did not start. This is just an option in case you do not want to go by the script file approach.

 

[sivaprasadfeb14]

You can also make use of writing to a log file concept.
Refer Post #5 here.

The very first stage of every process could be writing to the log file with something like "Process XX started" along with some details from the Calc stage Environment functions like Server name, Resource etc. Set the script file to run in the Windows Scheduler at 5 minutes after your above mentioned times (eg; 00:05 AM, 1:05 AM etc). From the script file read the latest message in the log file and if the message does not have "Process started" or is empty then shoot an email to your Support team indicating that Process XX did not start. Writing a line of text to a text file doesn't involve any configuration, only the Append to file action with the correct folder path. A new text file with the current date-time stamp can be generated on each run or may be you can append an earlier file in which case anyways the actual log message is going to contain the current date-time stamp.

Instead of the script file you can also have a Blue Prism process do this checking and email sending, but there are caveats like what if this BP process itself had problems in starting, and things like you need to have a free resource to run this process etc.

Another option is to have the first stage of the process to send an email to the Support team that the process has started. But again, this stage could fail while sending the email. In this case the On Support team should be made aware that if an email is not received within 5 minutes of 12 AM, 1 AM... then it could mean that the process did not start. This is just an option in case you do not want to go by the script file approach.

 

[sivaprasadfeb14]

Thanks for your Inputs VJ, It makes sense of having a log file with BOT trigger details and building an email logic. I'll try the same and will let you know the outcome.