| [30] Instructions on how to use InternetSupervision |
1 2 3 4 5
|
|
# 12 Voice Contact Days of Week
You should select the days of the week in which you would like to be contacted at that particular number. For example, if you select "12345", you will only be contacted on weekdays.
Numbers correspond to days of week are as follows:
1 - Monday
2 - Tuesday
3 - Wednesday
4 - Thursday
5 - Friday
6 - Saturday
7 - Sunday
NOTE: You should make sure that there is a contact available every day of the week. We can only call contacts that are available at the time of the failure. For example, if a failure occurs over the weekend and all your contacts are only available during the weekdays, we will not call anyone on your voice contact list. Therefore, failure notification will not be delivered to any of the voice contacts.
|
|
|
# 29 Port
When using the TCP Port service, you should set the "Port" value to the TCP/IP port that you want to monitor. When using any of the other services (SMTP, POP3, IMAP4, etc.), the "Port" value is automatically set the the default port of the monitored service (e.g. 25 for SMTP, 110 for POP3) and cannot be changed.
|
|
|
# 21 Alternate City Check
This feature is available for the HTTP/S service of paid accounts. When your website cannot be reached from the primary monitoring station in Chicago, IL, InternetSupervision will issue a second check from a different geographic location: Detroit MI, Washington DC, 2nd station in Chicago IL, or Santiago Chile.
If the website fails for the second time from the "alternate city", the monitoring station will attempt one more check from the primary station in Chicago. If the website fails all three checks, "failure event" will be generated. If your website fails from Chicago, but works OK from the "alternate city", "failure event" will not be generate. This feature helps decrease the number of false alarms.
|
|
|
# 27 Reminder Frequency
The time between consecutive failure reminders. You can specify a unique frequency for each of the "service contacts". This frequency has to be greater than or equal to your "check frequency". For example, if your service check frequency is "30 minutes", you can elect to receive reminders at the following frequencies: 30 minutes, 1 hour, 2 hours, 3 hours, 4 hours, 8 hours, or 12 hours. On the other hand, if your "check frequency" is 60 minutes (as it is always with the free accounts), you cannot lower the reminder frequency below "1 hour".
NOTE: If your check frequency is "5 minutes", we will not send you a reminder every 5 minutes since this would cause you to receive too many emails. Rather, the minimum reminder frequency is always "15 minutes" - even if your check frequency is "5 minutes".
|
|
|
# 22 Estimated Next Charge
The approximate number of days (or months) before your "Available Balance" reaches zero. This value is based on your current "Estimated Monthly Price". InternetSupervision will automatically charge your credit card when your "Available Balance" approaches zero - less than 5 days remaining.
|
|
|
# 16 HTTP Headers
HTTP HEAD Request. This is the only service type that is available to the FREE monitoring accounts. You can use this service to monitor your HTTP (not HTTPS) URLs. Our monitoring station will attempt to connect to your URL and issue a HEAD request to download only the http headers (e.g. HTTP/1.1 200 OK, Server:, Last-Modified:, Content-Type:, Content-Length:, etc) and not the actual page contents. The system will follow at most 5 automatic redirects (status code 302).
HTTP Headers service cannot be used if you want to look for specific expected and/or unexpected text in the content of the web page. If you need this functionality you will need to upgrade your account and use the HTTP/S service.The monitoring station's browser identifier (HTTP_USER_AGENT value) will be set to "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; UrlMonitor)".
The referrer of the monitoring request (HTTP_REFERER value) will be "http://internetsupervision.com/urlmonitor". The IP address will be different depending on which geographic location is making the request. A request that does not respond within 30 seconds will be considered to have "failed".
|
|
|
|