Transaction failure timeout - test level alert
Hi All,
I'm using Test level alert - "transaction failure" with "Retry on error" enabled.
Does anyone know the timeout value of first try and the 2nd try? Could these timeout values configure?
I guess the first try will be timeout in 60 seconds.... then it will "retry" after a few seconds and wait another 60 seconds as timeout.....so I should be able to get the email alert in 2 minutes time?
Much appreciate for any comments.
Thx
Sylvian
Thanks for all reply. The 30 mins reminder works for me. :)
Timeout values are managed in the script and default to 60s. Retry on error only triggers on certain errors, typically the types of error that cause an actual error, not a timeout.
Your logic is correct if the error only occurs after timeout in which case you would have to wait till end of second test for the alert trigger to fire, but please check the retry on error documentation here to determine whether the error you are experiencing is handled or not.
Thanks for your reply, Mark. The idea of "Retry on error" is really good to reduce false alarm.
What I want to check is website availability, i.e. "website no response to user", so it may cause by extremely slow website or website was down or public Internet problem....
Do you think my current configuration work for this situation?
Test Level alert = Transaction Failure
Monitoring node = 1
Node threshold = 1
Number of consecutive error = 1
Retry on error = ON
Reminders Frequency = 30 min
Much appreicate your help.
Sylvian
Hi Sylvian,
The alert configuration looks good. As Mark stated, Retry on error only triggers on certain errors, typically the types of error that cause an actual error, not a timeout. Check the retry on error documentation here to learn more about which errors will trigger Retry on Error.
Thank you,
Nyna
Hi Nyna,
Thanks for your comment. I checked the documentation but not quite understand how "Reminders Frequency" work.
---- doc says -----
- Reminders will be sent as long as test runs are still in the status that triggered the alert. Set the reminder so that at least one test run can occur before a reminder would be sent. For example, if the test frequency is every 15 minutes and the reminder frequency is only 5 minutes, reminders will be sent before the next test run can show whether the test is still in an alert status or has improved.
Many thanks for your help.
Sylvian
Frequency time is related to when the initial alert was triggered and add the frequency time upon that. With your example, say the alert was triggered at 9:15, if frequency set as 30 mins, it will check for alert status at 9:15 +30 mins which will be 9:45. It will check for the most recent alert status for each node, if the alert was still on, you will get a reminder email. In this case, Even test fail @9:30, you will not get reminder email since reminder frequency is 30 mins. (You might get All sites failure alert email if all nodes were failing @9:30).
And yes, the reminder alert will be sent out every 30 mins continuously until the test becomes successful.
Recommend you evaluating how often you need to be notified while test is failing before you set up the reminder frequency.
As you have configured it, the test will send REMINDERS only after the failure state was alerted and 30 minutes have passed since the alert was triggerd.
The test will continue to run every 15 minutes and either CLEAR the alert if it passes or if it fails on consecutive runs, send NOTHING (after having sent the FIRST alert email of course).
The reminder email will be sent every 30 minutes until the failed test passes again.
