Open topic with navigation
AlertSite’s real-browser monitors and mobile web monitors navigate your website to make transactions, like user logins, searches, purchase orders and so on. These monitors have many settings that control how transaction monitoring works.
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.
The monitoring plan used for this monitor.
The URL to monitor (only for single-step monitors).
Run Interval (Minutes)
How often the monitor checks your website. Possible values depend on your monitoring plan.
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. 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.
TCP Traceroute on Error
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 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 captures are stored for your account’s data retention period.
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.
Browser Timeout (Secs)
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 Step Timeout, because an event can include several HTTP requests.
Continue Playback on Timeout
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.
Alert on Content Change
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.
Fullpage Interval (Minutes)
How often the monitor measures fullpage response time for your website. This interval must be a multiple of Run Interval. Select -1 to disable fullpage measurements.
Object Timeout (Seconds)
Alert on page asset errors
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.
Alert and report if page assets are missing or new
Select this check box to send an alert if some page assets are missing or new assets have been added since the last check.
Alert and report if the size of a page asset changes
Select this check box to send an alert if the size of some page assets has changed since the last check.
Enable Transaction Trace
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.
- AppDynamics transaction tracing is supported in AlertSite Enterprise only.
- DéjàClick monitors that use Internet Explorer do not support transaction tracing.
Read-only. The number of pages (actions in DéjàClick terms) in the transaction.
Note: These options are only for Firefox real-browser monitors. They are not supported for Chrome and Internet Explorer monitors.
Firefox real-browser monitors can report not only network timings, but also user experience metrics – browser-related timings and optional page rendering timings. The following options control how the monitor collects these metrics:
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).
- This option is available only for Usage-Based Monitoring plans.
- Collecting the above-mentioned metrics consumes 0.5 extra measurement credit for every action (page) in the transaction.
- To collect these metrics, you need to record the transaction using Firefox. Before uploading the script to AlertSite, you need to replay it with the Replay for User Experience option enabled. When uploading the script, you must select Mozilla Firefox as the browser for monitor runs.
Show only base-page UX timings
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.
Select one or more locations to monitor you website from. For details, see Selecting Locations for Monitoring.
Here you can configure availability and performance alerts for the monitor or individual steps. To receive alerts, you need to have alert recipients configured. By default, the monitor sends alerts to all configured recipients, but you can target alerts to specific recipients by selecting recipient groups for this monitor.
Monitor Alerts and Step Level Alerts
If the monitor has multiple steps, you can configure alerts for the whole monitor or individual steps. Use these tabs to switch between monitor-level and step-level configuration.
Select the recipient groups that will receive alerts from this monitor. The recipient groups must have been previously created in Alerts > Alert Recipients.
If the monitor is not assigned to any recipient group, it sends alerts to all the recipients configured in your AlertSite account.
Note that adding a monitor to the recipient group overrides any step-level associations for that recipient group. So if you want to add individual steps to a group, remove the monitor from that group first.
Select this check box to send alerts when the monitor detects errors like HTTP errors, timeouts, or incorrect website content. The monitor status turns red in these cases.
Monitor-specific notes that can be included in email and JSON alerts (availability alerts only), up to 255 characters long. Note that to actually add these notes to alerts, you need to configure alert templates to 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.