Browser

Browser checks perform full-page render of a URL, using a specified version of Firefox, Chrome, or Internet Explorer.

With Browser checks, you can execute performance monitoring of all application components including style sheet rendering, image loading, and video streaming, and connections other content sources.

Subtypes

Firefox

*Soon to be Deprecated* Firefox check uses Mozilla Firefox to access the URL.

Chrome

Chrome checks use Google Chrome to access the URL.

Internet Explorer

An Internet Explorer uses Microsoft Internet Explorer to access the URL.

Scenarios

Checks can contain a Selenium browser automation scenario.

Using scenarios in your Web check allows you to verify that the site behaves as expected.

You can add a scenario to your browser check from the check configuration view.

Add Scenario

Upload Scenario

Click Add Scenario

The Add Scenario Dialog is shown.

Enter a Name for the scenario
Click Choose File

The file browser is shown.

Browse to the directory where you have the scenario file stored
Select the appropriate file
Click Open

The scenario is uploaded.

Click Save

The dialog is closed, and the scenario added.

Debug Scenario

The Debug Scenario view allows you to replace, edit or test the scenario.

Click Debug Scenario

The Debug Scenario view is shown.

Upload

The scenario can be replaced by a different scenario, or a newer version of the same scenario by uploading a locally stored scenario file.

Upload Scenario

Click Upload New File

The file browser is shown.

Browse to the directory where you have the scenario file stored
Select the appropriate file
Click Open

The scenario is uploaded.

Test

You can do a quick manual test run of scenarios added to your check.

Test Scenario

The settings for the test run is under the heading How would you like to test your scenario

Item	Description
URL	URL to run the scenario on.
Browser	Browser type and version to use for the test.
Location	Location to run the test from.
Custom Headers	Additional HTTP Header to send together with each request.
Test Scenario	Run the test.

Testing

While the test is running, progress is displayed next to the run button.

You can cancel the test at any time by clicking Cancel.

Result Summary

Success

When a scenario test run is successful, this is indicated by the execution summary:

Failure

If any of the steps in the scenario fails, this is indicated in the summary.

Screenshots

If the scenario is configured to use screenshots, they are displayed as part of the result summary.

Add

You can add commands to the list.

Add Command

Click Add Step

Select a command from the dropdown list

Double-Click the Target

Enter the target for the command

Double-Click the Value

Enter a suitable value

Click Save Scenario

Commands

The list of commands in the debug view shows each step in the scenario, and allows you to add, delete or modify steps.

Commands List

Column	Description
Command	Name of command.
Target	Target for the command.
Value	Command value, if any.

Reorder Commands

Commands in the list can be reordered by clicking the command row, and dragging it to a new position.

Download Scenario

To download a scenario to the local computer:

Click Download Scenario

The scenario is downloaded to the default download folder for your browser.

Mask Values

When command values contain sensitive information, they can be masked. This will prevent the value from being displayed in results.

Example

Let’s assume you use a scenario with the following commands:

Command	Target	Value
open	`/`
selectWindow	`null`
type	`id=username`	`user1`
type	`id=password`	{{$ Unknown macro: {maskapicaPassword} }}
clickAndWait	`_input`unnamed link

If you want to mask the value secretPa$$word in the Check Result page the following steps are required:

Add the command Store to store the password as a variable with the prefix maskapica

Use this variable with the actual command which uses the password.

Your commands should now look like this:

Command	Target	Value
store	`secretPa$$word`	`maskapicaPassword`
open	`/`
selectWindow	`null`
type	`id=username`	`user1`
type	`id=password`	{{$ Unknown macro: {maskapicaPassword} }}
clickAndWait	`_input`unnamed link

When Synthetic Monitoring runs a check using this scenario the result will be saved with the executed scenario commands list as the example above. When Synthetic Monitoring shows the check result on the check results page Synthetic Monitoring will recognize that there is a command value which starts with maskapica.

The command’s target will be masked on the the check results page:

Command	Target	Value
store	`*******`	`maskapicaPassword`
open	`/`
selectWindow	`null`
type	`id=username`	`user1`
type	`id=password`	{{$ Unknown macro: {maskapicaPassword} }}
clickAndWait	`//input`unnamed link

Execution Log

After a test run has ben executed for a scenario, a test execution log becomes available.

View

The execution log is collapsed by default:

To show the full execution log, click the expand button

Column	Description
	Order of execution.
Name	Name of command.
Target	Target for the command.
Value	Command value, if any.
Severity	Severity of error, if any.
Offset	Start time.
Duration	Execution time.

Success

Details for a successful test run are shown in the execution log:

Failure

If any of the steps in the scenario fails, any failed steps are indicated in the execution log.

####

The errors are also displayed in the list of commands in the Debug:

The Edit Scenario dialog allows you to add, replace, or download scenarios for the check.

Edit Scenarios

Click Edit Scenario

The Edit Scenario Dialog is shown.

Item	Description
Name of Scenario	Identifier for display purposes.
Created	Timestamp for when the scenario was created.
Last Updated	Timestamp for when the scenario was last edited.

Configure Scenario

A scenario consists of a scenario/script .prxdat file (or a .zip containing the script file and resource files) that has been compiled to a .class file.

Item	Description
Filename	Name of the file(s)
Description	Scenario description from the scenario file.
Last Updated	Timestamp for when the scenario file was uploaded.

Individual files can be deleted from the scenario with the delete file button.

The scenario can be replaced by a different scenario, or a newer version of the same scenario by uploading a locally stored scenario file.

Upload Scenario

Click Choose File

The file browser is shown.

Browse to the directory where you have the scenario file stored
Select the appropriate file
Click Open
Click Upload New File

The scenario is uploaded.

Click Save Scenario

The dialog is closed.

Using the Browser Check Wizard

Check Creation Wizard

With the browser check wizard (applicable for any browser) you can create a check and configure the basic settings.

Step 1: Name and Description

In the first step, you can add a check name and relevant information.

Step 2: URL, Scenario And Location

The second step allows you to configure the basic properties

Options

Item	Description	Comment
URL	URL to access.
Browser Version	Browser version to use for the check.	Depending on the version, additional options may be available.
Scenario	Scenario file.
Location	Locations for the check.	Note: If you select multiple locations, a separate check will be created for each location.

Buttons

Item	Description
Add	Add.
Debug	Debug .
Edit Script	Edit the script file.

Step 3: Interval, Thresholds & Monitor Groups

In the third step, you can define how often the check is to run, basic reporting settings and add administrative settings.

Frequency

Item	Description	Comment
Frequency	Time between data retrieval.	If set to `manual`, the check is only run on demand.

Thresholds

Item	Description	Comment
High Warning Threshold	Severity level Threshold calculation method and settings.	A warning is triggered above this value.
High Error Threshold	Severity level Threshold calculation method and settings.	Error is triggered above this value.
Low Warning Threshold	Severity level Threshold calculation method and settings.	A warning is triggered below this value.
Low Error Threshold	Severity level Threshold calculation method and settings.	Error is triggered below this value.
Treat 3rd party URL as Warning	Errors generated by third party URLs are handled as Severity level events.

Groups

Item	Description	Comment
Monitor Groups	Monitor Groups for the check.

Step 4: Confirm & Create

The final step provides an overview of the check configuration and allows you to create it.

Click Create to add the check and open the Configuration view.

Record WebSockets Option

The WebSocket Option, found under Browser Check Behavior, allows you to record WebSocket stream communications.

Results

When the check records WebSockets, you can get a detailed view of the recorded data by expanding the relevant result Waterfall Diagram row to show the details about the WebSocket recording.

View

Item	Description
Record Websockets	Turn WebSocket stream recording on or off.

NTLM

The NTLM section allows you to configure Authorization settings for NTLM.

Configuration

Option	Description
NTLM	Turn NTLM On/Off.
Protocol	Protocol version. Select `1` / `2`
Domain	The Windows (AD) domain for the user.
Username	User name for login.
Password	Password for login.

New Browser Check

Browser

Subtypes

Firefox

Chrome

Internet Explorer

Scenarios

Add Scenario

Upload Scenario

Debug Scenario

Upload

Upload Scenario

Test

Test Scenario

Testing

Result Summary

Add

Add Command

Commands

Commands List

Reorder Commands

Download Scenario

Mask Values

Example

Execution Log

View

Success

Failure

Edit Scenarios

Configure Scenario

Upload Scenario

Using the Browser Check Wizard

Check Creation Wizard

Step 1: Name and Description

Step 2: URL, Scenario And Location

Options

Buttons

Step 3: Interval, Thresholds & Monitor Groups

Frequency

Thresholds

Groups

Step 4: Confirm & Create

Record WebSockets Option

Results

View

NTLM

Configuration