Flow to trigger e-mail when either Ping or services stopped
we have HP OO studio and central. We are looking to create a flow in studio for below scenario and latter on,will create content pack and import on central.
After that we want to schedule the same flow.
Flow to monitor the ping check, HP tools process/services and generate email notification if any of the action fails.
we have multiple HP tools in our production environment. We are looking a work flow if any services is down (sitscope,OMi,OBR etc) then OO central schedular will trigger an e-mail notification for same. we had already created out of the box workflow, However not able to provide condition like if services "stopped" then will tigger e-mail.
The short answer would be in your flow every step that connects to a failure, or whichever response you use to mark that the flow ended unexpectedly (failed to get information, or status is not up) simply connect a send mail operation between the step and the failure response. In this case if anything other than service/server is up you will get notified every time the flow runs.
In our case, i hace created and schedule the same with 1 hourly frequency and we are receving the auto e-mail notification of workflow output.
However Customer said, they do not want Hourly notification and they are looking If any services is failed then OO will trigger notification to thier Inbox. do let us know is it possible or not?
Thanks for help!!!
As i previously said only send the email notofications for failures, not success. If you have too many false positives of service down then you need to refine the validation criteria.
I have attached an example of this with regards to the ping flow. Now in that method the flow will only send mail if the host cannot be pinged (host down) or if the losst packet rate is above a certain threshold (network issues). Other than that no matter how many times it runs it will not send e-mails.
There is a different way to handle this, however it is more ressource consuming. Basically the second method requires you to remove the eamil notifications from all the service monitoring flows and then just run periodically a flow that checks the executions related to monitoring and if there are any failures in that time period send an email notification. This is much more complicated to do and (from my point of view) more error prone than the first option, however it still can be done.