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
"

I like to know when my services are down, and how much time does it take to recover.

"
- LP
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
 
More
:
Home > Our monitoring network
Our agent list (139 agents) 
Location Status Company name
Qom, Iran, Islamic Republic of Working
Farrokh Shahr, Iran, Islamic Republic of Working
Hyderabad, Telangana, India Working
Helsinki, Finland Working
Amsterdam, Netherlands Working
Sydney, Australia Working
Dublin, Ireland Working
Bucharest, Romania Working
Prague, Czech Republic Working
Tehran, Iran, Islamic Republic of Working
Freemont, United States Working
Zurich, Switzerland Working
Sofia, Bulgaria Working
Tehran, Iran, Islamic Republic of Working
Berlin, Germany Working
Brescia, Italy Working
Novokuznetsk, Russian Federation Working
Kochi, Kerala, India Working
Luxembourg, Luxembourg Working
Tehran, Iran, Islamic Republic of Working
Shiraz, Iran, Islamic Republic of Working
Mashhad, Iran, Islamic Republic of Working
Paris, France Working
Singapore, Singapore Working
Tokyo, Japan Working
Ulaanbaatar, Mongolia Working
Tehran, Iran, Islamic Republic of Working
Tehran, Iran, Islamic Republic of Working
Victoria, Seychelles Working
Stockholm, Sweden Working
Dnipro, Ukraine Working
Minsk, Belarus Working
Cheyenne, WY, United States Working
Quincy, WA, United States Working
Zhejiang, China Working
Tehran, Iran, Islamic Republic of Working
Singapore, Singapore Working
Dublin, Ireland Working
Gibraltar, Gibraltar Working
Moscow, Russian Federation Working
Hangzhou, China Working
Manassas, VA, United States Working
Yekaterinburg, Russian Federation Working
Orlando, FL, United States Working
Rasht, Iran, Islamic Republic of Working
Mexico City, Mexico Working
Kuala Lumpur, Malaysia Working
New York, NY, United States Working
Vilnius, Lithuania Working
Mykolaiv, Ukraine Working
Santa Ana, Costa Rica Working
Lansing, MI, United States Working
Hamedan, Iran, Islamic Republic of Working
Ho Chi Minh City, Viet Nam Working
Patras, Greece Working
Budapest, Hungary Working
Tabriz, Iran, Islamic Republic of Working
London, United Kingdom Working
Amsterdam, Netherlands Working
Novosibirsk, Russian Federation Working
Tomsk, Russian Federation Working
Tehran, Iran, Islamic Republic of Working
Vladivostok, Russian Federation Working
Khmelnytsky, Ukraine Working
Bangkok, Thailand Working
Tehran, Tehran, Iran, Islamic Republic of Working
Jakarta, Indonesia Working
London, United Kingdom Working
San Antonio, TX, United States Working
Seoul, Korea, Republic of Working
Amsterdam, Netherlands Working
Meppel, Netherlands Working
Montreal, Quebec, Canada Working
Kansas City, MO, United States Working
Chisinau, Moldova, Republic of Working
Chisinau, Moldova, Republic of Working
Nuremberg, Germany Working
Sao Paulo, SP, Brazil Working
Tehran, Iran, Islamic Republic of Working
Katowice, Poland Working
Lenexa, Kansas, United States Working
Columbus, OH, United States Working
Munich, Germany Working
Dronten, Netherlands Working
Moscow, Russian Federation Working
Kazan, Russian Federation Working
Montreal, Canada Working
Los Angeles, CA, United States Working
London, United Kingdom Working
Singapore, Singapore Working
Moscow, Russian Federation Working
Paris, France Working
Gravelines, France Working
Meppel, Netherlands Working
Waco, TX, United States Working
Moscow, Russian Federation Working
Almaty, Kazakhstan Working
St.Petersburg, Russian Federation Working
Clarks Summit, PA, United States Working
Tehran, Iran, Islamic Republic of Working
Ballito, South Africa Working
Santa Fe de la Vera Cruz, Argentina Working
Melbourne, VIC, Australia Working
Strasbourg, France Working
Kyiv, Ukraine Working
Berlin, Germany Working
Kharkiv, Ukraine Working
Houston, TX, United States Working
Istanbul, Turkey Working
Kuala Lumpur, Malaysia Working
Belgrade, Serbia Working
Singapore, Singapore Working
Orlando, FL, United States Working
Amsterdam, Netherlands Working
Amsterdam, Netherlands Working
Quincy, WA, United States Working
Zagreb, Croatia Working
Amsterdam, Netherlands Working
Cheyenne, WY, United States Working
London, United Kingdom Working
Zurich, Switzerland Working
Istanbul, Turkey Working
Bucharest, Romania Working
Vilnius, Lithuania Working
Sofia, Bulgaria Working
San Antonio, TX, United States Working
Montreal, Quebec, Canada Working
Amsterdam, Netherlands Working
Dallas, TX, United States Working
Moscow, Russian Federation Working
Dublin, Ireland Working
Kwun Tong, Hong Kong Working
Kochi, Kerala, India Working
Nairobi, Kenya Working
Belgrade, Serbia Working
Amsterdam, Netherlands Working
San Jose, CA, United States Working
Noida, India Working
West Europe Working