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 > HostTracker_under_Azure

Those, who actively involved with the Web, should know HostTracker, a company from Ukraine, which has been supporting one of the leading global web monitoring services since 2004. Its goal is to monitor site health and accessibility in near-real-time access. Using alert message system, HostTracker allows to reduce downtimes, to improve quality of service for users, to quickly localize troubles...

​Those, who actively involved with the Web, should know HostTracker, a company from Ukraine, which has been supporting one of the leading global web monitoring services since 2004. Its goal is to monitor site health and accessibility in near-real-time access. Using alert message system, HostTracker allows to reduce downtimes, to improve quality of service for users, to quickly localize troubles, and etc.

Architecturally, HostTracker includes a server-based hub, acting both as a data collector and control center, and a series of software agents, launched in various regions – typically using the equipment operated by major providers, hosters and affiliates. The geographically distributed architecture provides common system reliability and also allows collecting data in terms of access speed, bandwidth and other key performance characteristics on regional level – a critically important feature for the international business.

The first version of HostTracker, which is still functioning and providing services for tens of thousands of customers, was Linux based. Today, it is supported by nine control servers, located and organized in two DPCs on collocation principle, and few dozens of agents. Considering that the final objective of web monitoring is focused on increasing the uptime of client-based web resources – whereas 95% of HostTracker customers were able to increase it up to 99% – then, performance and accessibility of the service itself are not just critical, but rather fundamental parameters that influence the whole business. Theoretically, HostTracker should demonstrate accessibility close to 100%. However, an extensive growth of the service made this task hard to solve.

HostTracker was facing constantly increasing network traffic – a problem for seamless operation of the service. Inability to add new control servers on-the-fly, difficulties when maintaining not uniform and multiple-aged hardware was another limiting factor. Moreover, the desire to develop the service through wider protocol and network service support was meeting certain obstacles. “Unfortunately, for Linux there was a limited choice of ready-to-use solutions and libraries, while inventing something completely new was difficult”, says Artem Prisyazhnyuk, HostTracker director. “We had an idea of reviewing the stack of technologies we used for a more sophisticated one and after taking a closer look at the .NET platform, its potential in terms of scalability and network support, I realized that was exactly the thing we had been looking for.”

It was sure that migrating to a completely different platform should be a complex task – the project extended over three years. However, it was like blessing in disguise: during this period, the world has seen the cloud computing that seemed an ideal tool for solving both the scalability problem and putting aside one’s own whole infrastructure. Besides, the PaaS model allowed to remove most of the effort in terms of administering the solution and to control the application as a self-contained entity, to the extent of complete automation, and thus, Windows Azure had in fact no alternatives.

As a result, the second version of HostTracker, commercial operation of which started in May 2012, is already functioning under Windows Azure. Its central ingredient is realized as Web Role and associated with SQL Azure Database – it provides external portal, analytics and report generation, control of monitoring applications. The latter are ensured with instances of Worker Role, which also use SQL Azure Database to store their data and to provide the service scalability depending on the network loading. Agents are functioning as they did before, with the viability of their transfer to Windows Azure being considered.
Now, HostTracker uses HTTP/HTTPS and ICMP protocols to monitor specific ports, including various methods (HEAD/POST/GET), and etc.
 

HostTracker instant check



Alarm reporting is available via email, SMS and instant messages. The customer can receive reports with statistics about resources being controlled and their performances. You can spend only 6 minutes to make monitoring settings for five sites, while the average response time in case of failure is limited by a couple of minutes, and it takes 1-3 minutes more to inform the customer about the problem. Using this service, anyone can check any site, including access from various regions.

 As a result, if on the one side the transfer to the .NET platform itself gave us the potential to modernize HostTracker, to optimize the application architecture and realize new internal functions, then, on the other side, the migration to the cloud allowed to refuse from less important, though time consuming activities such as administering the solution, and, first of all, to reach necessary performance indicators. Microsoft, for all basic Windows Azure services, declares 99,9% accessibility and guarantees monthly refunds, should this indicator be lower. This creates a firm ground for operating such services like HostTracker, as the accessibility is the most critical parameter for these applications. Using the cloud infrastructure also provides a better protection for the service: unauthorized access to the application and many types of attacks are effectively excluded, while the data safety is ensured by triple reservation.

HostTracker received another advantage from abandoning its own infrastructure. The service’s performance characteristics are also rather critical, for they directly affect the failure reporting system operation. In this respect, Windows Azure is virtually a drainless source of computing power. This means that by timely starting additional monitoring instances you can support HostTracker functioning parameters on the necessary level. Moreover, the cloud environment is exactly what you need in order to make this process almost fully automatic, excluding further need for direct control.

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