It would be great if we have an alert mechanism, where bot couldn't start the process due to some bot connection issue/bot lost/other issues. In such scenarios, we don't have any alert mechanism now, which informs about it.
Taking advantage of this line of reasoning, I believe that we could have a warning automation mechanism in warning too, maybe an SMTP system that warns by email maybe that automation has been in warning for a long time.
It would be great if Blue Prism provides that but;
There are some workarounds to monitor your resource PCs.
1- Monitor IPs and ports with your company's monitoring tools. When there is an issue, the tool automatically triggers an ITSM ticket. 2- Blue Prism writes all logs of warnings, infos and errors to Windows Event Viewer. An alert mechanism can be build in Event Viewer. 3- (Not recommended) Listen BPAResources table in Blue Prism database and send alert. 4- There is an open source tool in GitHub. I guess it is developed by Blue Prism team. (not sure). You may want to take a look at this.
The DRM is a much broader solution for managing runtime resources and schedule adherence, but it also includes the capability to add logic to notify an administrator of issues. You could perform that notification in any number of ways (ex. send and SMS using the Twilio skill).
The Resource PC Monitor is a simple service that will check in periodically with configured runtime resources to see if they are reachable on the network (basically a ping). If a resource fails to respond to 2 requests in a row, a notification is sent via email. I believe there's an option being added now to support SMS too.
