Real-Browser Monitor (DéjàClick) Settings

Click this button to download the DéjàClick script used by the monitor so that you can update it. See Updating DéjàClick scripts below.

The monitoring plan used for this monitor.

The URL to monitor (only for single-step monitors).

How often the monitor checks your website. Possible values depend on the Measurement Plan selected for this monitor.

How long the monitor waits for a response to each network request (for example, HTTP GET) before reporting a timeout error.

Leave a note for yourself or other users. Note text can be up to 1000 characters long. This note will appear on the AlertSite Dashboard when you hover over the icon. The note can also be included in alerts.

The monitoring mode controls if locations check your website simultaneously or sequentially, and when they send alerts. See Monitoring Modes for possible values and details.

For each monitor, you define a location pool. Rotation means the monitor uses a subset of this location pool (say, 2 out of 10 locations) on every run, cycling through the locations. If rotation is not used, the monitor checks from all of its locations every time.

Notes:

• Rotated locations are not available for monitors that use private locations.

• Usage-Based Monitoring plan allows rotated locations for the following monitoring modes: Round Robin, SLA (MultiPOP), Global Notify, and Global Verify.

• Legacy plans (Performance Pro, SLA) support rotating through locations only for the Round Robin and SLA (MultiPOP) modes.

If Rotate Locations is selected, you need to specify the number (subset) of locations to use for each monitor run. This value ranges from 1 to the total number of locations you selected for the monitor.

When using the Round Robin or SLA (MultiPOP) monitoring mode, you need at least 2 locations per interval.

This option applies to Firefox monitors only. If your monitored website supports IPv6, AlertSite can test your site over IPv6. For that, select the Use IPv6 option and select one or more IPv6-enabled locations for this monitor. See IPv6 Monitoring for details.

Applies only to monitors using the Usage-Based Monitoring plan. If local retry is enabled, then whenever the monitor finds an error, it will repeat the test from the same location to see if the problem is temporary. If the retry succeeds, no alert is triggered. For more information, see Local Retry and Global Verification.

Before releasing AlertSite updates, SmartBear runs regression tests to make sure that both existing and new functionality work correctly. Select (or clear in AlertSite 1.0) this check box to include your monitor in SmartBear regression testing, so we can make sure your monitors will work correctly after AlertSite updates. Participation is voluntary.

If this is selected, the monitor runs a TCP traceroute to your website when it detects a network connectivity problem (status 1 or 2), and sends results to all email alert recipients. The traceroute shows the path that data packets are taking from a monitoring location to your server, and can help administrators and engineers troubleshoot problems.

Real-browser monitors can capture web page screenshots, source code, and HTTP headers for all or some transaction steps. You can view these captures on the Monitor Runs dashboard, and also in the Detail report by clicking the camera icon.

Select the needed capture level:

• Disabled – Do not capture web page data.

• Error Only – (Default) Capture web page data only for failed steps.

• All Actions on Error – Capture web page data for all actions (pages) in the transaction, but only if there was an error.

• All Actions – Capture web page data for all actions (pages) in the transaction, even if there are no errors.

• All Events on Error – Capture web page data and screenshots for all events (clicks, text input, list selection, and so on) in the transaction, but only if there was an error.

• All Events – Capture web page data and screenshots for all events in the transaction, even if there are no errors.

The captures are stored for your account’s data retention period.

The All ... options are available for Usage-Based Monitoring plans only and consume 0.5 measurement credits per every web page capture. For example, All Events will consume 0.5 credits for every event (mouse click, hover, text input, form submission, and so on) in the transaction.

The All ... options are not supported for monitors that use private locations.

Tip: You can also configure email alerts to include the screenshot and HTML of the page where the transaction failed. To do this, edit your alert recipients and select the Attach screen capture to e-mail alerts and Attach server response to e-mail alerts options. Alert content does not depend on the monitor’s Capture Level.

How long the monitor waits for a test event (recorded user interaction) to finish before reporting a timeout error. Recommended value: 90 seconds. Must be greater than Timeout (Secs) (or Step Timeout in AlertSite 1.0), because an event can include several HTTP requests.

Controls what to do when the Browser Timeout is reached. Select this check box to ignore the timeout and continue the test; clear to stop the test and send an alert.

If this is selected, the monitor tracks the size of the last page in the test, and sends alerts if the page size changed since the last check.

The browser version used to run the monitor at AlertSite global monitoring locations.

Possible values for Chrome monitors:

• Default – the default version is Chrome 85
• Chrome 74
• Chrome 85

Possible values for Firefox monitors:

• Default – the default version is Firefox 78
• Firefox 52
• Firefox 78

This option applies only to Firefox and Chrome monitors. If a client SSL certificate is required to access the monitored site, upload this certificate to AlertSite, and then select it from this list. The certificate will be automatically installed to the AlertSite global locations selected for this monitor. For details, see Using SSL Certificates and Java Keystores.

In addition to the regular response time, AlertSite can measure fullpage response time, which includes the web page itself and all of its images, CSS, scripts and other linked assets. This option enables or disables fullpage measurements. Depending on the monitor, this option can be an On/Off switch, or a list of intervals to choose from. In the latter case, this interval must be a multiple of Run Interval.

How long the monitor waits for a page asset (image, JavaScript file, CSS file, and so on) to load before reporting a timeout.

Select this check box to send an alert if the monitor finds an error when loading an image, script, CSS file, or other page asset.

Select this check box to send an alert if some page assets are missing or new assets have been added since the last check.

Select this check box to send an alert if the size of some page assets has changed since the last check.

This option enables or disables AppDynamics transaction tracing for the monitor (see AppDynamics Integration). If it is selected, AppDynamics captures server-side transaction snapshots for each monitor run. The snapshots contain code-level details like the slowest methods and SQL queries, and can help troubleshoot performance issues. You can access these snapshots from the Monitor Runs dashboard.

If this check box is selected, the monitor collects two additional page rendering timings that reflect perceived user experience:

• First Paint – The time it takes the browser to start displaying the page.

• Above the Fold – The time it takes for all visible content rendered on the page to stabilize. If the Fullpage interval is set, the Above the Fold time includes the load time of page assets (images, scripts, style sheets, and so on).

Notes

Available only if Enable UX is selected. Controls how the monitor calculates browser-related metrics (DOM Load and Page Load) for web pages that contain frames. Select this check box to collect timings only for the base page without frames; clear to collect total timings for the entire page including frames.