faq209 wrote:How does that work. How come there aren't any alarms apparent in that
monitoring demo?
Thanks for asking.
First, we didn't put any alarms into the demo because, well, who would we be alarming with a text message or an email? Besides, for the demo we chose websites and/or web applications that we know are quite reliable.
But in practice you use the eValid Flag Processing commands to set conditions and, when a problem occurs, to take alternative action.
For example, if your script has "OnErrorGoScript recover.evs" then if/when some subsequent command generates an Error message then control is given to "recover.evs" immediately. The current script is discarded and you continue with whatever you need to do in the recovery process. This probalby is an email or text message send along the appropriate channel.
Or, you could have your "recover.evs" repeat the test you just ran and which failed to make SURE that the failure was not an accident or a glitch. Also, this sanitization of the alarm tends to reduce the false alarm rate to a low level without compromising the actual value of the test.
The eValid Team