Open topic with navigation
This topic describes the configuration settings for Selenium monitors. You can change the monitoring locations, run interval, timeouts and other settings.
The monitor name that appears in dashboards and reports. For example, Customer Login.
– the monitor is enabled.
– the monitor is disabled.
– the monitor sends alerts. You can specify which alerts to send (availability, performance or both) in the Alerts section.
– the monitor does not send any alerts.
Click this button to download the JAR file used by this monitor. You can run it locally by using this command (provided that you have Java installed):java -jar <path>\filename.jar
Click this button to upload a new JAR file to replace the one currently used.
Note: After you upload a new JAR file, the monitor is automatically disabled. You need to run a successful test on demand before you can enable the monitor again. Click to run a test on demand.
The monitoring plan used by the monitor. You cannot change the plan for existing monitors.
Run Interval (Minutes)
How often the monitor checks your website. Possible values depend on your monitoring plan.
Step Timeout (Seconds)
Note: Timed out pages are indicated in run results but do not affect the overall monitor status (unless you designed your Selenium script to treat timeouts as errors). The monitor status (OK/error) is determined by the exit code of the JAR file.
Leave a note for yourself or other users. This note will appear on the AlertSite Dashboard when you hover over the icon. Note text can be up to 255 characters long.
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.
- Rotated locations are not available for monitors that use Private Node Server locations (private monitoring stations installed on your local network).
- 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.
Locations Per Run
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.
If Monitoring Mode is Round Robin or SLA (MultiPOP), you need at least 2 locations per interval.
Enable Local Retry
Used only for Usage-Based Monitoring plans. Controls the monitor behavior when it finds errors. Select this to retry the test from the same location to see if an error was just a temporary error. Clear to suppress the retry on errors.
Note: The retry consumes extra measurement credits.
Allow AlertSite QA Testing
Before releasing AlertSite updates, SmartBear runs regression tests to make sure that both existing and new functionality work correctly. Select 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.
AlertSite can capture additional data about each web page used in your Selenium script. This includes:
- web page screenshots,
- HTML source code of web pages,
- request and response headers for all HTTP requests made during the page load (this includes the page itself, its images, scripts, Ajax requests, and so on),
- Selenium run log with the console output from the JAR file.
This option specifies the amount of extra data to capture:
- Disabled – Do not capture any extra data.
- Error Only – Default. Capture extra data only for web pages that have error status, such as page timeout.
- All Actions on Error – Capture extra data for all pages, but only if the monitor has error status. This option consumes 0.5 measurement credits per web page capture.
- All Actions – Capture extra data for all pages, even if there are no errors. This option consumes 0.5 measurement credits per web page capture.
You can access the captured data from the Monitors > Runs screen, using the corresponding buttons in the expand run results. You can also see the captures in the Detail report by clicking the camera icon.
Note: You can also have the Selenium run log attached to email alerts if you configure alert recipients with the Attach server response to e-mail alerts option. This functionality does not depend on the monitor’s Capture Level.
When a browser loads a web page, it fires events to notify about the page loading progress, such as:
- DOM Load (DOMContentLoaded) – the page’s HTML has been completely loaded and parsed, without waiting for stylesheets, images and subframes to finish loading.
- Page Load (load) – the page is fully loaded with all images, styles and other resources (except for Ajax and Flash content).
The browser timeout is the timeout to receive the DOM Load and Page Load events for a page. It is a “hard” timeout, meaning the Selenium script will be stopped if these events are not received within the timeout interval.
Object Timeout (seconds)
Timed out objects do not affect the monitor OK/error status. They are only indicated in the reports by status 7002.
Select one or more locations to monitor you website from. For details, see Selecting Locations for Monitoring.
Here, you can enable and disable availability and performance alerts for the monitor. Note that to receive alerts, you need to configure alert recipients. By default, the monitor sends alerts to all configured recipients, but you can target alerts to specific recipients by using recipient groups.
Select this to send alerts when the monitor detects errors like HTTP errors, timeouts, or incorrect website content. The monitor status turns red in these cases.
Arbitrary monitor-specific information (up to 255 characters) that can be included in availability alerts sent via email. For example, you can specify the login and password used in a transaction – so the alert recipients do not have to look them up in the monitor configuration.
Default alerts do not include these notes. You will need to configure custom alert templates that would include the $ALERT_NOTE variable.
Select this to send alerts when the monitor response time exceeds the specified value. See Performance Alerts for a description of available settings and to learn how to set up these alerts. Note that, for multi-step monitors, the response time thresholds should include the total response time for all test steps.