WPM Playback Intermittently Down

Been running this gauntlet for almost 2 years now, and the reason we require 2 failures (20 minutes of downtime) before alerting out. It cuts down on false alerts, but takes 20m+ to detect an issue. It is product related bc our simpler sites are solid in WPM and never/rarely fail. It wouldn't be that bad if we could immediately retest after a failure, but WPM is limited in what it can do at runtime and we have to wait an entire run interval to verify. My team has spent 100s of hours banging our heads against our desks trying to crack this egg and the only hope is a better product. Angular JS.

thwack212:  one way we get around this is to have the same URL run from 2 different servers. We split our up geographically into 2 different data centers, but you wouldn't need to do that.  

Then we put those monitors in a group, change the group to show mixed status and then alert off of the groups status.  This way if we have a monitor running every 10 min we don't have to wait 20 min for it to run twice.  If one monitor goes down the group status will go into warning.  If both monitors go down then the group status shows as down and triggers the alert.  This way we only have to wait 10 min for an alert.  We have found it to be very reliable, even with crappy websites. 

thwack212:  one way we get around this is to have the same URL run from 2 different servers. We split our up geographically into 2 different data centers, but you wouldn't need to do that.  

Then we put those monitors in a group, change the group to show mixed status and then alert off of the groups status.  This way if we have a monitor running every 10 min we don't have to wait 20 min for it to run twice.  If one monitor goes down the group status will go into warning.  If both monitors go down then the group status shows as down and triggers the alert.  This way we only have to wait 10 min for an alert.  We have found it to be very reliable, even with crappy websites.