POST method example
POST method example Example of monitoring a webform with POST method.

For example you have such simple form:
form action="some-site.com/some-script.cgi" method=post
input type=text name=login value=''
input type=password name=password value=''
input type=submit name='Submit' value='Login'
/form
User fill this form with value login: Peter and password: 1234 and click submit. If everything is Ok, script prints "LoginOk" on the result page.
For making a monitoring task to control this script, create task with next fields:

URL: some-site.com/some-script.cgi
Http Method: choose POST
In "POST parameters" field you should add three strings:
login=Peter
password=1234
Submit=Login
In "Content check" field: LoginOk
Results: HostTracker with every check will fill this form and assume that it is OK if the set keyword LoginOk is returned.

  • CM.Glossary.WebsiteMonitoring
  • CM.Glossary.HTTPMethods
more glossary
"

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

"
- LP
Domain Expiration Monitoring

HostTracker gives you a unique opportunity to take an ultimate control over your website and increase its performance to new levels. Our service features lots of different handy tools that will let you monitor your website activity constantly and be the very first to know when you need to take actions...

In today’s fast-paced tech-savvy world, having a quality website monitoring service in place is a must to achieve top website speed, performance, and subsequent business success. HostTracker gives you a unique opportunity to take an ultimate control over your website and increase its performance to new levels. Our service features lots of different handy tools that will let you monitor your website activity constantly and be the very first to know when you need to take actions. All critical information will be brought directly to you through email, SMS or voice call, or via direct message on Viber, Skype, Hangouts, Telegram or Slack. All you need to do is decide how, when and where you want to receive these alert notifications. With our service on board, you will say goodbye to those pesky website problems caused by your hosting company, DDoS attacks and missed domain (SSL Certificate) renewal.

The nasty reality of expired domains

Here are a few reasons why dropping a domain name, even if it is fast recovered, is not a good idea:

  1. A heavy drop in search engine rankings and coming traffic.

  2. Undermined credibility. When it comes to domains there’s nothing worse than your domain name taken by others and used for malicious purposes. Yep, you got it right, domain hijacking is real! And once you’ve got your domain expired, you become very vulnerable to this kind of threat, yet you can’t guarantee safe user experience. This means you risk to lose your customer info, brand reputation, and money as well. Well, but that’s not all… What about your potential customers? Few would disagree that another important reason why many people are prone to abandon the particular website is its accessibility. No doubt, no one likes to wait. And if it comes to making a purchase online your potential customer will wait only 3 minutes prior to leave and never come back.

  3. Financial losses. Say, you’re the loyal client of particular bank or stock exchange, you’ll be definitely really upset to discover that you can’t check your financial info as the service seems to be down. Truly, the Internet is littered with tragic examples of how big companies including banks dropped domains and run into financial trouble because of that.

Let’s take a second to think about how hard it is to stay on track with the domain expiration. Actually, it's not quite that easy at all. Suppose you’ve got about 100-300 websites and even more email addresses. Moreover, every day you’ve got your Inbox bombarded with tons of different emails. Obviously, it’s really easy to scroll on some important information such as a reminder from your registrar in such a hectic situation.

If you don’t want to curse God for your memory lapses, consider jumping into some of the awesome monitoring tools like Domain expiration from HostTracker. With this tool in place, you won’t need to rely on your registrar. As you will be notified 30, 7 and 1 days before (and even after) the expiration of your domain by email or direct message.

Enabling notifications

Here are 5 simple steps to set HostTracker for sending you alerts of the impending domain expiration:

  1. Sign in.
  2. Upon successful login, navigate to Add check -> Domain expiration.

      3.  Enter your domain name or click on Add list if you have multiple domain names.

      4.  Click on the check boxes to select the contacts for notifications.

      5.  Click on Save when complete.

If you have Business or Enterprise packages, you’re opted to activate the domain/SSL expiration alert notifications for existing monitoring tasks.

Our service is still developing so should you have any questions, concerns or any comments to share, feel free to email our Support Team. You can also find us on Twitter, Facebook or Google+.

more blog
Thank you for feedback!
 
Sign In
Sign In
Sign Up
Prices & packages
Our monitoring network
Home > Blog > Escalatios

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.

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