Using monitors with 'Managed Services' on your dedicated server

Managed Services is an additional option that can be added to your dedicated server. After you have ordered Managed Services, the option will become available in the Control Center.

If you have not already, login to the Control Center at
https://www.webcontrolcenter.com/customer.aspx
and from the menu item SERVER click on DEDICATED/VPS MONITORING.

Dedicated customers who have purchased the "managed services" option can monitor web sites/mail services on the server to make sure they are up and running. If a monitored items "fails", then the customer (and support if desired) is contacted via email. If support is contacted, various "solutions" can be defined for support to try to fix the problem.

There are 4 monitor types that can be created:

HTTP: Monitor a web page (.htm, .asp, .cfm, etc.) to see if it is up
POP3: Monitor a POP3 mail service to see if the connection is active
SMTP: Monitor a SMTP mail service to see if the connection is active
IMAP: Monitor a IMAP mail service to see if the connection is active

To create a monitor:
1 - Click "add", choose a monitor type, provide the required information, click "save". Monitor will be marked as "OFF" (not active) initially.
2 - Test the monitor by clicking "test monitor". Keep testing until a successful result is obtained.
3 - Choose the monitor and click "on" to make it active.
NOTE: Only addresses inside our network can be monitored.

Editing/deleting monitors:
Monitors can be edited and deleted by click on the "edit" and "delete" buttons.

Enabling/disabling monitors:
Monitors can be "turned off" by clicking the "off" button, and "turned on" by clicking the "on" button. Always try not to turn on any monitor until successfully tested.

Monitor history:
Click on the "monitor history" button to see the testing history for each monitor. Select a day to see the history for that day. Each test is recorded as a SUCCESS or FAILURE based on the monitor criteria. You can see how often a web page or mail service has been down during that day.

"Failed" monitor
After a monitor fails for the first time, it is retried at one minute intervals until it succeeds again. If a monitor fails 3 consecutive times, then a notification e-mail is sent to the customer. Any consecutive failures beyond that point will not cause an e-mail to be sent. Once the problem is fixed, the "failed counter" resets to zero, allowing an e-mail to be sent if more failures occur later.

HTTP Monitor options
URL - Page that needs monitoring.
PORT - Usually 80 for http monitoring, however can be changed if needed
MONITOR EVERY: Ranges from two minutes to one month
START DATE/TIME: Time that monitor will activate
USERNAME/PASSWORD: If page is password protected, specify username/password here to get past web authentication
SEARCH STRING: If specified, the monitor will search the page for the search string. The monitor can be configured to fail/not fail based on finding the search string.
EMAIL ADDRESSES: Monitor failure notices will be sent here. Separate multiple addresses with semicolons
CONTACT SUPPORT: You can choose whether to allow support to reset the IIS service (attempted first if chosen) or reboot your server (attempted second) as well as give a specific task for support to try (attempted third). If the chosen tasks fail to resolve the problem, you can allow support to troubleshoot your server (attempted last).

NOTE: Support may charge the customer for fixing a server problem if tasks other than restarting a service or rebooting a server need to be done.

MAIL Monitor options
ADDRESS - IP or Domain for mail service to test.
PORT - Usually 110 for POP3, 25 for SMTP, 143 for IMAP, however can be changed if needed
MONITOR EVERY: Ranges from two minutes to one month
START DATE/TIME: Time that monitor will activate
EMAIL ADDRESSES: Monitor failure notices will be sent here. Seperate multiple addresses with semicolons
CONTACT SUPPORT: You can choose whether to allow support to reset the MAIL service (attempted first if chosen) or reboot your server (attempted second) as well as give a specific task for support to try (attempted third). If the chosen tasks fail to resolve the problem, you can allow support to troubleshoot your server (attempted last).

NOTE: Support may charge the customer for fixing a server problem if tasks other than restarting a service or rebooting a server need to be done.

Add Feedback