Scoutbees—ControlUp’s synthetic testing application—immediately picked up on the outage, and proactively alerted its users about the issue in their environment. The screenshot below was captured from a browser at 5:15 p.m. EDT.
Scoutbees correctly identified the issue as an authentication failure, giving our customers in-depth information on pinpointing the root cause of the problem!
Without Scoutbees, IT’s first line of information is usually end-users calling the help desk to complain about the error messages they get when trying to log in to their applications. In a case like this, they might tell your helpdesk that they were getting error “HTTP ERROR 503”:
“HTTP ERROR 503” doesn’t really provide much information about the problem. Googling the error message will return the generic “Service Unavailable.” You might think, “Service Unavailable? For Azure?” Further investigation would be required.
Being in IT, you might have authenticated into Azure, prior to the outage, to manage your resources. Given that, your experience would be inconsistent with your users, because Azure was working fine for you. “Azure is down? What? Could it just be my user’s home WiFi connection?”
In a situation like this, your help desk would get overwhelmed with calls from users reporting the same thing. Tickets would get escalated, and panic would set in, as you investigate what in the heck was going on. Is your first step checking social media to see if it’s just you experiencing the outage? Should it be?!
IT SHOULD NOT BE. With Scoutbees and its best-in-class synthetic testing, you’d have received a proactive alert about the outage and would have knows what was going on before it even popped up on Twitter:
With this information, you can give your help desk advanced warning or even proactively alert your users about a potential problem and to check your support page for outage information.
“Bee” Proactive. Try Scoutbees and proactively monitor your environment today!