Synthetic Monitoring: Diagnosing Errors

Table of Contents

• Introduction
• Demo Walk Through
• Step by Step

Introduction

Using Blue Triangle's dashboards and alerts, users can see when a synthetic monitor has found an error on their site. This article covers how to diagnose an error, how to determine the criticality of the issue, and finally, the work flow that follows.​ 

Demo Walk Through

Step by Step

Begin by opening the left hand menu and navigating to the Performance Overview page found under the Real Browser options in Synthetic Monitoring. ​

Once in the Performance Overview page you will find the Error Tracking and Performance Widget ​

You can change the Displayed Metric at the top of the widget. For further configuration you can use the settings gear icon in the upper right corner of the widget. From there, you can change the graph sizing, whether or not to prioritize Monitors in an Error State, and whether or not to show Metric Average. ​

To view or change the error tracking configuration of a specific monitor, select the gear icon next to the individual monitors. This page sets what the conditions for an error state are. ​

Going back to the Error tracking widget we see that each monitor is represented either in green, or red. Red indicating an error state.​ When you hover over a bar, details about the error will pop up. ​To further diagnose an error, click on a bar in a red area. ​

This will open the Synthetic Test Results page​ where we can see specific test failures. ​

If you hover over the result code, you will be able to see the error message, or what command failed.​ This can help quickly identify what went wrong.​

To investigate further, we can select the drop down button on the error result to display more details. ​

The main tabs to focus on will be Object Level Detail, HAR File, Screenshots, Filmstrips, Console Log, and the Test Event Log. ​

Under Test Event Log, the test is broken down by steps with time steps.​ Here, we can see exactly where the error has occurred. ​