Enable Monitoring (or Monitoring Is in AlertSite 1.0)
Monitor ID (in AlertSite UXM)
Read-only. The monitor ID that can be used in AlertSite APIs.
Name (or Site Name in AlertSite 1.0)
The monitor name that appears in dashboards and reports. For example, Customer Login.
Enable availability or performance alerts on the Alerts tab.
Set Notify on Error to Yes to enable availability alerts for this monitor or No to disable availability alerts. Performance alerts are configured separately by clicking the Performance Alerts button in the top row.
Measurement Plan (or Site Plan in AlertSite 1.0)
The monitoring plan used for this monitor.
Run Interval (Minutes) (or Check Every in AlertSite 1.0)
How often the monitor checks your website. Possible values depend on the Measurement Plan selected for this monitor.
Monitor Note (or Device Note in AlertSite 1.0)
The engine used to run your ReadyAPI or SoapUI test at AlertSite’s global monitoring locations. Possible values:
- Default – the default engine is ReadyAPI 1.9
- ReadyAPI 1.1
- ReadyAPI 1.9
- TestEngine – corresponds to ReadyAPI 2.8
The engine version defines the functionality that your API test can use. We recommend that you create API tests using the same version of ReadyAPI as the playback engine you will use.
|Note:||Private Node Server locations ignore this option and use the locally available engine.|
Monitoring Mode (or Monitoring Type in AlertSite 1.0)
The monitoring mode controls if locations check your API 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 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.
Locations Per Run (or Locations per Interval in AlertSite 1.0)
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.
Enable Local Retry (or Disable Local Retry in AlertSite 1.0)
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.
|Note:||The retry consumes extra measurement credits.|
Enable AlertSite QA Testing (or Disable AlertSite QA Testing in AlertSite 1.0)
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.
AlertSite can keep SoapUI logs from test runs for later analysis. The logs include complete requests and responses (URL, headers, body, HTTP status code) and the details of any errors occurred. This can help troubleshoot failed tests.
Select the level of logs to store:
Disabled – Do not store SoapUI test logs.
Errors Only – (Default) Store SoapUI logs for just failed test steps.
All Steps on Error – Store SoapUI logs for all test steps, but only if the test failed.
All Steps – Always store SoapUI logs, even for successful runs.
The last 2 values are available for Usage-Based Monitoring accounts only, and consume 0.5 measurement credits per capture.
You can view SoapUI logs:
- in the test step details on the Monitor Runs dashboard
- in the Detail report by clicking the camera icon.
You can also have the SoapUI log attached to email alerts if you configure alert recipients with the Attach server response to e-mail alerts option. This does not depend on the monitor’s Capture Level.
This section shows custom properties defined for your monitor. You can select a value for each property from the predefined list.