Distributed Monitoring
Distributed Monitoring Distributed monitoring is a method of website monitoring when the checking is performed from several locations.

Distributed monitoring is a method of website monitoring when the checking is performed from several locations. The main purpose for this is to exclude errors of checking server (which is always possible) from the site statistic and provide more precise result. Usually it is realized through the network of independent servers which check the sites one-by-one or simultaneously. The advangtages of such checks are listed below:

Checks are happening from different locations, just like the real users do.

If a single check fails - others may prove or decline the failure. So, probability of false downtimes is really low.

It is possible to overview the access and download speed from different countries and cities.

Possibility to catch network-related or DNS problems: site might be visible from your computer, but are you sure it works for everyone?

  • CM.Glossary.WebsiteMonitoring
  • CM.Glossary.Availability
more glossary
"Thank you so much for your service. We were suspecting problems with our hosting company but they denied any problems saying the issues must be at our end. We know we do have issues at our end but still suspected that wasn't the entire story. Your service was able to prove that they are indeed going down regularly - on average twice a week during the trial period. Thanks again for providing the information we needed to make a proper decision on this issue."
- B.
What could we check by using the cloud services? Part 2

  In the beginning, HostTracker company was founded on the basis of a simple website to provide free customer services. Though, a few years later, this startup developed a wide variety of tools serving to solve various problems, including different network issues. In a series of publications, we have decided to describe thoroughly all the features of our service, also to share our experience in the development of such projects with you and to mention interesting challenges that we faced. 

In the beginning, HostTracker company was founded on the basis of a simple website to provide free customer services. Though, a few years later, this startup developed a wide variety of tools serving to solve various problems, including different network issues. In a series of publications, we have decided to describe thoroughly all the features of our service, also to share our experience in the development of such projects with you and to mention interesting challenges that we faced. Moreover, for those seeking an example of how to sell something that had been made for themselves, our experience would be useful, as most of our features were developed due to our personal needs.

In the previous part of the review we have talked about the history of the service and the most basic functions - regular inspection of sites and servers, and what is more, notification of their efficiency. Before starting to describe more advanced features, we should write where do all these ideas come from and how to prioritize them. One of the key secrets often used by entrepreneurs is to follow the statement: all people are unique. All customers’ requests are unique, so you have to learn how to deal with them. Therefore the IT sector is utterly susceptible to this factor, as a great number of customers have profound knowledge and diverse experience. Nevertheless, part of the problems can be solved with available resources. However, the main feature of our work is that, frequently, we have to evolve something. Most of the HostTracker’s functions were developed or adapted due to the conveniences and needs of the particular people. We are also a part of that people, as having rather large infrastructure, and also need to have everything work properly. Therefore, we ourselves are the most picky client.


Precious little things

It worth noting, that in addition to different regular checks, there are other useful tools. They include monitoring of the domain and SSL certificate expiration time. This seems to be negligible, but could bring a lot of unexpected inconveniences to work. These functions appeared in HostTracker, when one of our personal domains had expired. Moreover, large companies also frequently face these problems, as the prolongation of the domain /certificate expiration time depends on the unreliable human factor. Therefore, a notification that the domain should be prolongated, is stored not only within spam folder (already overflowed with continuous marketing messages from your hosting company), but also to the folder with the data of website downs. As well as, the SMS notification capability still exists. That’s why these features are being so handy.

Another interesting feature is the domain check to see if they are blacklisted in DNS-based lists. These lists are independent and are generated separately using different algorithms. What is more, they were mainly created for filtering of the suspicious entities. Each administrator can configure own web server in different ways, for example, not to receive messages from the servers from a specific list. It helps fight off spam, malware spread, DDoS attacks and other problems. But all of these lists have their own algorithms, and there is no guarantee that in the result of any coincidences your website wouldn’t appear in any of these blacklists. Moreover, according to the statistics, this is happening on a regular basis with the most innocent sites. For example, no one can guarantee that a hacker wouldn’t use your nearby IP for different spam attacks. In this situation, the entire range of IPs would be considered as unreliable. What are the consequences of that?  Your messages wouldn’t be delivered to customers, the site wouldn’t be so easily found in search system and so on. Furthermore, you will find out this problem when the changes become critical or even irrevocable. Therefore, the monitoring and notification of DNSBL are also essential.

The content check

Here is a good example of how the usage of functions may exceed developers expectations. We have mentioned about several such cases earlier. Actually, nowadays a lot of things have a web interface whilst for others – it could be easily created, if needed. Therefore, it was developed not only the check function of whether the page was loaded completely using simple parsing, but also another mind-boggling things of this check. Adapting to different customer requests, this feature has become very flexible. It may look for one or plenty of words from the list at once. Moreover, it may detect the emergence of certain phrases. This feature may also raise as an error the whole line that contains the keyword. For instance, if there is a kind of server-status page (“Server 1 OK” etc.) and it shows “Error”, then the message will be “1 Server Error”.  In this case, all diagnostic is already done, and you can start troubleshooting immediately.

What if it happens, that the server should be down?

In addition to the notification of the failures of the sites, HostTracker provides another important function – gathers statistics of each examined site. When the various buttons on the sites were popular – HostTracker’s button also often appeared with the figures of website attendance, the weather forecasts and other things like that. Now it is possible to use a widget, but still the button is also available for retro fans. In addition, statistics is very important for managers. They constantly want to know whether the website and administration of it are working properly. Therefore, there is another useful function - the maintenance planning. Even the most stable sites and servers must be updated or rebooted from time to time. At the same time, it’s not the desired to lose so-called “9s” in terms of uptime. Planning of the maintenance let us achieve two goals (together or separately). This includes: not to send error notifications and not to record errors to the statistics during a specific span of time. Of course, it seems to be a kind of cheating, but outlined maintenances are justified, especially in excluded time. In addition to this, different verifications have being done and written to the log during maintenances. It can be useful for webmasters and administrators, as log let determine exactly the duration of updating or restarting processes, any occurred errors, other breakages etc. Moreover, thanks to that, the whole process of error emergence could be tracked: from the stage when the server wouldn’t be available for some time to the stage when the application would return an error.

Maintenance can be scheduled as a one-time job or on a regular basis. For example, if the backup is done every night, or a new release - every Thursday. The only condition is that the maintenance schedule should be made up at least 12 hours prior to the site/server nearest suspension period of time. This is done to ensure that all maintenances won’t be responsible for any pity unexpectancies, and statistics provided by HostTracker will be trustful.

A kind of an epilogue

We are frequently asked why we are doing this. The same things could be done without HostTracker’s help.  And you know what - definetely, they could. Especially, if you need only one tool. Many people are talking, that the whole Business World is built on human laziness. By solving routine problems, HostTracker provides a slice of work-free and responsibility-free time in the customer’s schedule. Truly, not everyone is able to assemble a car by himself. We look up to people, who are eager to create something good for personal needs in our field, but most people don’t want to spend their free time for doing something like that.

Additionally, our clients are: non-IT specialists; IT specialists who have to report something to their managers; managers themselves; fans of reliability – they use their own tools and take advantages of someone else’s; and many other groups of people.

All in all, we are always looking forward to your comments.

more blog
Thank you for feedback!
 
More
:
Home > Our monitoring network
Our agent list (134 agents) 
Location Status Company name
Qom, Iran, Islamic Republic of Working
Hyderabad, Telangana, India Working
Amsterdam, Netherlands Working
Tehran, Tehran, Iran, Islamic Republic of Working
Sydney, Australia Working
Bucharest, Romania Working
Freemont, United States Working
Zurich, Switzerland Working
Sofia, Bulgaria Working
Tehran, Iran, Islamic Republic of Working
Berlin, Germany Working
Brescia, Italy Working
Tehran, Iran, Islamic Republic of Working
Shiraz, Iran, Islamic Republic of Working
Mashhad, Iran, Islamic Republic of Working
Paris, France 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
Tehran, Iran, Islamic Republic of Working
Singapore, Singapore Working
Dublin, Ireland Working
Moscow, Russian Federation Working
Manassas, VA, United States Working
Meppel, Netherlands Working
Phoenix, Arizona, United States Working
Tehran, Iran, Islamic Republic of Working
Denver, Colorado, United States Working
Istanbul, Turkey Working
Rasht, Iran, Islamic Republic of 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
Sofia, Bulgaria Working
Arezzo, Italy 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
Dronten, Netherlands Working
New York, NY, United States Working
Dusseldorf, Germany 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
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
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
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
Arezzo, Italy Working
Moscow, Russian Federation Working
Dublin, Ireland Working
Kwun Tong, Hong Kong Working
Kochi, Kerala, India Working
Nairobi, Kenya Working
Belgrade, Serbia Working
Centurion, Gauteng, South Africa Working
Amsterdam, Netherlands Working
San Jose, CA, United States Working
Noida, India Working
West Europe Working