This topic describes the configuration settings for FTP monitors. You can change the monitoring locations, run intervals, timeouts and other settings.
You must be an Admin, Co-Admin or Power User to change the monitor settings.
It may take a few minutes for the changes to take effect.
You can set the default settings for new monitors in > Settings > Preferences > Monitor Defaults in AlertSite UXM, or in Account > Manage Account in AlertSite 1.0.
Monitor Name (or Site Name in AlertSite 1.0)
The monitor name that appears in dashboards and reports. For example, Customer Login.
Monitoring (or Monitoring Is in AlertSite 1.0)
Alerting (or Notify on Error in AlertSite 1.0)
– 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.
Select 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.
Host (or URL in AlertSite 1.0)
The host name of the FTP server, optionally with a directory path. For example:
If a directory path is specified, the monitor will use the
CWD command to change the working directory to the specified one.
|Note:||To monitor the server by the IP instead of the host name, leave Host blank, unselect Resolve DNS, and enter the IP Address (IPv4 only).|
Run Interval (Minutes) (or Check Every in AlertSite 1.0)
How often the monitor checks your FTP server. Possible values depend on the selected Measurement Plan.
The connection timeout, in seconds. If AlertSite cannot establish a connection to your server within this time interval, it will report status 1 (TCP connection failed), and an alert will be triggered. Default: 30 seconds.
Monitor Note (or Device Note in AlertSite 1.0)
Monitoring Mode (or Monitoring Type in AlertSite 1.0)
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 (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.
If Monitoring Mode (or Monitoring Type in AlertSite 1.0) is Round Robin or SLA (MultiPOP), you need at least 2 locations per interval.
Enable Local Retry (or Disable Local Retry in AlertSite 1.0)
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 (or select in AlertSite 1.0) to suppress the retry on errors. To learn more about that, see Local Retry and Global Verification.
|Note:||The retry consumes extra measurement credits.|
Allow AlertSite QA Testing (or Disallow 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.
Attempt file upload to FTP server
If this option is selected, AlertSite will test the file upload and download on your FTP server. An upload/download test works as follows: AlertSite generates a small test file with a random name, uploads this file to your tested server, then downloads this file, and compares the uploaded and downloaded files. The uploaded file will be removed afterwards.
If your FTP Host includes a subpath, such as ftp.example.com/path/subpath, AlertSite will upload the file to the specified directory on the server.
|Note:||File upload requires that your FTP server supports passive FTP. You also need to specify the FTP Username and FTP Password of a user with read/write permissions on your server.|
If this is selected, AlertSite will connect to your FTP server using the Host name. If this is unselected, AlertSite will use the IP Address instead.
This option is displayed only if Resolve DNS? is unselected. It specifies the IP address (IPv4) of the tested FTP server. AlertSite will connect to the server using this IP address instead of the Host name.
Optional. The port number on your FTP server that AlertSite will connect to. The default ports are 21 for FTP and 990 for FTPS (FTP over SSL).
TCP Traceroute on Error (or TCP Traceroute on Nework Error in AlertSite 1.0)
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.
These options apply to FTPS (secure FTP) monitors only.
Version of SSL Protocol to use when connecting
If your FTP server requires a specific SSL or TLS version for client connections, select the desired version from the list. Otherwise, select Auto-Detect, and the monitor and your server will select the protocol automatically.
Use user-supplied client certificate when connecting
If your FTP server requires a client-side SSL certificate to access it, you need to upload your certificate to AlertSite. To do this, go to > AlertSite 1.0 > Configure > SSL Certificates, upload the certificate, and then assign it to your monitor. For detailed instructions, see Using SSL Certificates and Java Keystores. This approach works if you use AlertSite’s public locations.
If you use private locations, please send the certificate to SmartBear Support, along with your API monitor name, location name, and also your company name and customer ID from the > Account screen. You will be informed when the certificate is in place. After that you can do a test on demand to verify the monitor.
You need to specify the FTP Username and FTP Password if your FTP server requires authentication, or if Attempt file upload to FTP server is selected. In the latter case, the specified user must have read/write permissions on your FTP server.
For anonymous access, use anonymous as the user name. Any password should work, but it is common to use the password guest or your email address. Some FTP servers explicitly require passwords in the form of an email address.
Select one or more locations to monitor you FTP server from. For details, see Selecting Locations for Monitoring.
Here you can configure availability and performance alerts for the monitor. 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.
Recipient Groups (or Notifier Groups in AlertSite)
Select the recipient groups that will receive alerts from this monitor. The recipient groups must have been previously created in Alerts > Alert Recipients (or Notifiers > Notifier Groups in AlertSite 1.0).
|If the monitor is not assigned to any recipient group, it sends alerts to all the recipients configured in your AlertSite account.|
|Note:||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.|
Availability Alerts (or Notify on Error? in AlertSite 1.0)
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. To add these notes to alerts, you need to configure alert templates to include the
$ALERT_NOTE variable. For details, see Adding Monitor-Specific Notes to Alerts.
Enable performance alerts if you wish to be notified 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.
In AlertSite 1.0, click the Performance Alerts button in the top left corner of the monitor configuration screen to view or change the performance alert settings.
For multi-step monitors, the response time thresholds should include the total response time for all test steps.