HTTP methods
HTTP methods HTTP methods define actions, wished to perform to a specific site.

GET method is used when the page is loaded from server to your browser. If it works, your web page is available to load. It is the most common method among all, when you type a site address in your broswer - this method is used to show you the site content.

HEAD method is similar with GET, but it load from server only headers of your page. It is useful if You want to test just accessibility of a web page or review its headers.

POST method is used to send information from you to server. If a page includes text field(s) for filling, POST method is used when you click button "submit" (or whatever is name of that button). It brings information you have typed into those fields to server. So, if there are some text fields on your page, you can use this method. If it works, your web page is available to use, and text, typed into fields on your page, is able to be transferred to the server. An example of using POST method for Website Monitoring is provided in this article (You provide specific keywords, which are inserted into text fields).

  • CM.Glossary.WebsiteMonitoring
  • CM.Glossary.HTTP
  • CM.Glossary.POSTMethodExample
more glossary
"

HostTracker is reliable and very useful to me and my team.

"
- D.
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!
 
Privacy policy
Sign In
Sign Up
Prices & packages
Our monitoring network
Home > Privacy policy

What information do we collect?

  • We collect information from you when you register on our site or place an order.
  • When ordering or registering on our site, as appropriate, you may be asked to enter your: name, e-mail address, mailing address, phone number or credit card information. You may, however, visit our site anonymously.

What do we use your information for?

  • Any of the information we collect from you may be used in one of the following ways:
  • To personalize your experience (your information helps us to better respond to your individual needs.
  • To improve our website (we continually strive to improve our website offerings based on the information and feedback we receive from you).
  • To improve customer service (your information helps us to more effectively respond to your customer service requests and support needs).
  • To process transactions. Your information, whether public or private, will not be sold, exchanged, transferred, or given to any other company for any reason whatsoever, without your consent, other than for the express purpose of delivering the purchased product or service requested.
  • To send periodic emails. The email address you provide for order processing, may be used to send you information and updates pertaining to your order, in addition to receiving occasional company news, updates, related product or service information, etc.

How do we protect your information?

  • We implement a variety of security measures to maintain the safety of your personal information when you place an order.
  • We offer the use of a secure server. All supplied sensitive/credit information is transmitted via Secure Socket Layer (SSL) technology and then encrypted into our Database to be only accessed by those authorized with special access rights to our systems, and are required to keep the information confidential.

Do we use cookies?

  • Yes (Cookies are small files that a site or its service provider transfers to your computers hard drive through your Web browser (if you allow) that enables the sites or service providers systems to recognize your browser and capture and remember certain information.
  • We use cookies to understand and save your preferences for future visits.

Do we disclose any information to outside parties?

  • We do not sell, trade, or otherwise transfer to outside parties your personally identifiable information. This does not include trusted third parties who assist us in operating our website, conducting our business, or servicing you, so long as those parties agree to keep this information confidential.
  • We may also release your information when we believe release is appropriate to comply with the law, enforce our site policies, or protect ours or others rights, property, or safety. However, non-personally identifiable visitor information may be provided to other parties for marketing, advertising, or other uses.

California Online Privacy Protection Act Compliance

  • Because we value your privacy we have taken the necessary precautions to be in compliance with the California Online Privacy Protection Act. We therefore will not distribute your personal information to outside parties without your consent.
  • As part of the California Online Privacy Protection Act, all users of our site may make any changes to their information at anytime by logging into their account and going to the 'Profile' page.

Host-Tracker Microsoft Bot Framework

  • Our Host-Tracker bot is enabled by Microsoft Bot Framework. The Microsoft Bot Framework is a set of web-services that enable intelligent services and connections using conversation channels you authorize. As a service provider, Microsoft will transmit content you provide to our bot/service in order to enable the service.
  • For more information about Microsoft privacy policies please see their privacy statement here: http://go.microsoft.com/fwlink/?LinkId=521839.
  • In addition, your interactions with this bot/service are also subject to the conversational channel's applicable terms of use, privacy and data collection policies.
  • To report abuse when using a bot that uses the Microsoft Bot Framework to Microsoft, please visit the Microsoft Bot Framework website at https://www.botframework.com and use the “Report Abuse” link in the menu to contact Microsoft.

Your Consent

  • By using our site, you consent to our web site privacy policy.

Changes to our Privacy Policy

  • If we decide to change our privacy policy, we will post those changes on this page, and/or update the Privacy Policy modification date below.
  • This policy was last modified on 11.11.2016

Contacting Us

Share:
Send to Twitter Send to Facebook Send to LinkedIn Share on Google+
Blogs:
HostTracker blog HostTracker page on Facebook