Active Monitoring
Active Monitoring Active Monitoring is the way to check the site performance by simulation of visiting by real users.

Active Monitoring is the way to check the site performance by simulation of visiting by real users. It is done by external service, usually with distribyted networks. The checking servers create the requests like the real clients, who are trying to download a web page. Doing it on regular schedule, allows to check if the page is available from the web. If not - there is a possibility to catch and report the error. The difference between the bot and a real person is visible only for bulky pages with lots of content - in order to save the traffic, monitoring systems usually download only a part of such pages, which is enough to make sure the site is Ok.

Active monitoring is an independent eye on your site. The checking is not connected to your company and web hosting, and so provides the clear third-party view of the situation. HostTracker service uses active monitoring to supervise web sites.

  • CM.Glossary.WebsiteMonitoring
  • CM.Glossary.Downtime
  • CM.Glossary.DistributedMonitoring
  • CM.Glossary.PassiveMonitoring
more glossary
"

I use it for free an just for having mail of when my website is down, and it's work very well, so I want to thank you.

"
- RA
Host-Tracker under Windows Azure
Those, who actively involved with the Web, should know Host Tracker, 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, Host Tracker allows to reduce downtimes, to improve quality of service for users, to quickly localize troubles...
Those, who actively involved with the Web, should know Host Tracker, 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, Host Tracker allows to reduce downtimes, to improve quality of service for users, to quickly localize troubles, and etc.
Architecturally, Host Tracker 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 Host Tracker, 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 Host Tracker 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, Host Tracker should demonstrate accessibility close to 100%. However, an extensive growth of the service made this task hard to solve.
Host Tracker 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, Host Tracker 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 Host Tracker, 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, Host Tracker uses HTTP/HTTPS and ICMP protocols to monitor specific ports, including various methods (HEAD/POST/GET), and etc.



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 Host Tracker, 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 Host Tracker, 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.  
Host Tracker 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 Host Tracker 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.
more blog
 
More
:
Home > Our monitoring network
Our agent list (105 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
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
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
Orlando, FL, United States Working
Kochi, Kerala, India Working
Amsterdam, Netherlands Working
Zagreb, Croatia Working
Amsterdam, Netherlands Working
London, United Kingdom Working
Zurich, Switzerland Working
Istanbul, Turkey Working
Bucharest, Romania Working
Vilnius, Lithuania Working
Sofia, Bulgaria Working
Amsterdam, Netherlands Working
Dallas, TX, United States Working
Moscow, Russian Federation Working
Kwun Tong, Hong Kong Working
Kochi, Kerala, India Working
Nairobi, Kenya Working
Amsterdam, Netherlands Working
San Jose, CA, United States Working
Noida, India Working
West Europe Working