Web Hosting
Web Hosting Web Hosting is a service which makes a site available from the Internet.

Web Hosting is a service which makes a site available from the Internet. It provides a physical place for your site (server) and Internet connection, also it may provide DNS services. Hosting companies differs from those who own huge datacenters to the small ones who rent couple of servers somewhere.

How to choose a hosting? You should pay attention to several important things: features, price, support and uptime.

Features include disk space, database usage, bandwidth, monthly traffic etc. Requirements totally depend on your site. It is clear that personal page has different requirements than a well-known online market.

Price. You may even find completely free hosting, just look if the service satisfies your needs.

Support. How long does it take to solve a problem with your site? What is an avarage response time? Your site is down for a week, and noone cares - is that possible?

Uptime - what is actual running time of the site.

Reliable hosting is very important for business. Using website monitoring services may help to evaluate the hosting service and check how often do the problems really appear.

  • CM.Glossary.Uptime
  • CM.Glossary.Downtime
  • CM.Glossary.WebsiteMonitoring
  • CM.Glossary.DNS
more glossary
"

I happy, that use you services.

"
- MG
Escalations. Typical scenarios

As many people know, HostTracker is a sites efficiency monitoring system. One of its main functions is to notify the user of any problems promptly. The efficiency of the notifications and the acceptable level of “detalization” are important. If you send alerts at each “sneeze”, the person will not find the important information in this flow...

I was woken up by an SMS at three a.m.
My site dropped for three minutes, and it raised back itself.
But I could not go back to sleep.

True-life story

As many people know, HostTracker is a sites efficiency monitoring system. One of its main functions is to notify the user of any problems promptly. The efficiency of the notifications and the acceptable level of “detalization” are important. If you send alerts at each “sneeze”, the person will not find the important information in this flow.

We have provided several mechanisms that will help the right people to get the necessary notifications:

  • Separation of the notifications into several groups according to their criticality;
  • No notifications at short-term failures;
  • Report the problem to the manager promptly;
  • Report a prolonged failure to the administration;
  • Use the free alerts first – email, gtalk, and then the paid ones – SMS or phone call;
  • At the contact level – set the working time when this contact should receive the alerts.

There are three types of notifications:

  • The website has “dropped”;
  • The website is still “down”;
  • The website “rose

The “dropped” and “rose” are clear. The notifications “site is still down” are sent at each test fail, but only at the confirmed drops. The fails confirmation algorithm was described in the article “False alerts exclusion”

For each site-contact pair you may enable or disable the appropriate notification type. The setting can be located in the contact properties as well as in the general “matrix” at the “Notifications subscribtion” page.

Escalation and the notifications detalization level.

Suppose, two people are responsible for the site:

  • Administrator
  • Manager

Let's try to implement the following scenario:

  • In the event of a “drop” we want to send an email message to the administrator immediately;
  • If the site does not rise within 15 minutes, we send an SMS to the administrator;
  • If the site is “down” for more than an hour, then we send an SMS to the manager.

Adding the contacts for the users. While adding, draw attention to the “Notification Delay” window.

We appear to have three contacts with the following delays:

  • Administrator (email) – no delay;
  • Administrator (SMS) – 15 minutes delay;
  • Manager (SMS) – 1 hour delay.

According to this configuration the administrator will get all the failures notifications to the email, but SMS notifications will be sent only if the site is “down” for more then 15 minutes. The manager will receive only SMS about major failures lasting more than an hour. Setting up the contact working schedule

Suppose that one administrator can not cope, and we hired one more administrator. The first one works during the first half of the week, the second one works during the second half. Accordingly the notifications should be sent to the administrator “on duty” To set this scenario the window “Set the contact working hours” is used in the contact settings.

In this case the first administrator will receive the SMS notifications from Monday to Thursday inclusive. Additionally, you may divide the notification for different employees according to the time of day, for example appointing day and night administrators.

Conclusions: with the help of relatively simple mechanisms we may cover most notifications fine-tune user scenarios.

more blog
Thank you for feedback!
 
Become partner
Sign In
Sign Up
Prices & packages
Our monitoring network
Home > Our monitoring network > Become partner
Datacenter info
Deployment info
Choose at least one method of deployment proposed below (FTP, RDP, Panel) and fill in its parameters
FTP, RDP setups are preferable as they enable new agent version deployment automation
Your company info
 
Share:
Send to Twitter Send to Facebook Send to LinkedIn Share on Google+
Blogs:
HostTracker blog HostTracker page on Facebook