How to create devices

Configuring a script execution

Each UserView device contains a script with the sequence of steps created using the EveryStep Scripting Tool. You can create a new script, import a script into EveryStep Recorder from an existing device or upload it from a local machine. 

Once the UserView script has been created and saved, you can configure the script execution settings on the Script tab.

The best way to modify a complex monitoring script (add new/edit existed steps) is to open and edit it directly in the EveryStep Scripting Tool

Recorded Script

The field displays the script that was recorded using EveryStep Recorder. To edit the script, click the Edit Script button, and modify the script with EveryStep Recorder. See also: Editing a UserView Script.

Scripting Mode

This field displays the browser type selected in the script, device type, and recording resolution.

Completion Timeout (in seconds)

Enter the number of seconds the task should wait for a response from the web page before ending the task and returning an error. If this is left blank the default timeout for a task is 120 seconds.

Simulate Return Visitor

If you want to see how a web page performs for a frequent visitor, or someone who already has elements from the page cached, you can turn on the return visitor flag on the task edit screen.

Simulate a Return Visitor immediately revisits the web page a second time and only records the results of the second visit. Results may differ from a first visit (which always starts with an empty cache) based upon how the browser handles certain items, such as the expiry of elements on the page.

Record Video on Each Run

Record Video on Each Run will record a video capture for every single monitoring session.  If this option is not turned on, the task will only record a video on the first session of a day that errors or on the first error detected from a location in a given error period.

Abort Script on First Error

In some cases, a monitoring error may affect the execution of subsequent monitoring steps and cause a significant delay in alerting. To stop script execution on the first monitoring error, select Yes.

For example, a monitoring error received on the client login step execution leads to failures on the subsequent monitoring steps. In cases where there are a significant number of the monitoring steps in the script, it will take some time for Dotcom-Monitor to finish the script execution and send an alert. To receive alerts faster, it’s recommended to activate the Abort Script option. 

If you do not need to abort the script on minor network errors, add the elements that return errors to the ignore list.

Due to the time, it takes to process the detected error and abort the script, the device report may contain data on several steps after the error occurred.   

DNS Options

The DNS Options feature allows users to choose how domain name server (DNS) requests are conducted during a monitoring task.

To specify the mode of resolving hostnames, in the DNS Resolve Mode section, select one of the available modes. For more details on the feature configuration, see DNS Mode Options.

The Custom DNS Hosts section contains the mappings of IP addresses to hostnames.

To specify the mapping, enter the IP address and the host name in the corresponding fields.

Examples:

192.168.107.246   example.com user.example.com userauth.example.com tools.example.com
192.168.107.246   example.com
192.168.107.246   user.example.com
192.168.107.246   userauth.example.com

See also: DNS Mode Options.