Response Time Monitoring
Response time monitoring Response time monitoring is testing how fast is your site.

Response time monitoring is testing how fast is your site. It might be accessible, but bad performance can still make it unattractive for the clients. The monitoring of the response time allows you to check how the site acts as the time goes on. Do any of the scheduled tasks, like backup, updates etc affect the performance? Does the site works well for the whole world, or some regions of interest could meet a confusing delay?

HostTracker provides a possibility to check the reaction of your site. Select Response time check on the main screen:

Create ContentCheck Task

Then, select the largest satisfactory response time for the site. Is this value is exceeded, you receive a notification. Also, all the statistics is stored in the check log, and response graph is generated. You may check this data at anytime.

Create ContentCheck Task

NOTE! Response time depends on the distance between the datacenter of your site and our checking server. It might be large enough for a remote country. To decrease this effect, select a checking region in advanced options.

Create ContentCheck Task
  • CM.Glossary.WebsiteMonitoring
  • CM.Glossary.ContentCheck
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
Snapshot - instrument for site supervision

How does the site look like when I’m not looking at it? What if it looks bad or does not work at all? HostTracker offers an instrument for site supervision - snapshot feature. Let’s take a look at its practical application.

How does the site look like when I’m not looking at it? What if it looks bad or does not work at all? HostTracker offers an instrument for site supervision - snapshot feature. Let’s take a look at its practical application.

What’s going on with my site?

Now it’s usual to use different services and applications for site maintenance and support, and sometimes they do report some problems. Often we feel the lack of information - Google Analytics or a similar service reports the downtime and renewal, but likely we will never know what exactly has happened. To investigate the issue, it is necessary to review the logs, write to hosting support and perform many others exhausting actions, frequently - with no result. There are also more interesting cases - when a site is not available from a certain country or is not downloaded completely. Such problems could long for months, or even years, till they are accidentally detected. One more important issue - content check. It will automatically review the content of the site and inform the responsible staff in case it has disappeared - for example, something has not been able to be downloaded from the database. But it’s hard to find the cause if the issue is short-term, because people usually do not sit in front of a laptop refreshing the page every minute. To resolve the problem, HostTracker offers a new feature - snapshot. It is very simple in use and does not require any additional adjustments. The service simply makes a snapshot of the checked page every time and saves it for review in two ways: page source code and html-view. This let you easily see how the page looks at the moment of failure, understand what’s wrong and fix the problem quickly without spending time for diagnostics. It saves lots of time for server administrator, developers and other concerned people.

How does it work

Doing the regular checks, our servers with predefined interval try to download the checked page. Additional algorithms could be used at the moment - the page could be parsed for keywords to make sure that this is the one we are looking for (there are cases when an error page returns 200, Ok, http code, or when redirection is activated in case of error). If there is no error - fine. But if there is, it will be written down into the HostTracker log, which is easily available from the web. Then, notification are sent and a snapshot is made.

The snapshots could also be found in the log - if several errors were detected, a different snapshot will be available from each one.


Though there are some remarks. First, we do not run javascript while making snapshot - same thing for regular check. Second, the error must be detectable. It means, the server must return something. In case of timeout or connection error - snapshot will not help, and only a corresponding record will remain in the log.

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

Website monitoring is a process of supervision over the performance of the site. HostTracker is a powerful tool which serves that purpose.

Website monitoring is a process of supervision over the performance of the site. Usually it is used to keep an eye on commercial sites or other pages for which high availability is very important.

Companies, which provide website monitoring services, let their clients to check a website, a server, port or other available from the Internet entity. The responses are collected and analyzed. Usually, the monitoring is performed from different locations, distributed over the whole world or the specific continent or country. Such monitoring is called distributed monitoringand helps to detect network-related issues as well as site or server-related. Also, distributed monitoring often makes possible to analyze the site performance from the places which are close to the real customers, instead of some distant locations which could have high latencies. The collected information could be found in a different form: email reports, graphs and different smart dependencies, to help the client to get a comprehensive view of the site's performance. Parameters like load time, speed and others can help to optimize the site performance. In case of critical error, monitoring services use variety of notification methods to deliver the alert to the client: SMS, voice call, instant messengers, email and others. This, together with immediate diagnostics, helps responsible persons like server administrators or developers to fix the site as soon as possible and minimize the duration of the failure.

Why is this important? For commercial sites, working time is proportional to their income. Roughly speaking, 2 hours of failure per day means that 1/12 part of the potential clients are lost. Even more - loyal customers also can find a more reliable competitor in case they can not receive their services/goods when they want. For other types of sites, like government, educational, NGO this is very important too. If people can't find the information fast, they'll find another source. Some parameters like site speed are important for search engines, others - database connectivity, for example - can greatly affect the convenience of usage of the site. Monitoring of some internal values like CPU load, memory consumption and disk space are important for administrators in order to prevent performance degradation. Another important purpose is verification of SLA (service-level agreement) of hosting provider. For technical issues, no site can be available 100% of time during long enough period. Sometimes servers are rebooted, updated or upgraded. So each hosting provider guarantee some specific value, which is called uptime, that shows how long can a site be down for technical reasons. Uptime is usually measured in percent. In this table it is shown for how long a site could be down for each uptime value:

  • 90%          876 hours
  • 95%          438 hours
  • 99%          87,5 hours
  • 99.9%       8 hours 45 minutes
  • 99.99%     52,5 minutes
  • 99.999%   5 minutes 15 seconds

If the real site performance does not correspond to SLA, it could be a reason for claim and refund request. Also, it can help the customers to select the best hosting for their needs.

Monitoring companies often provide some additional services, like vulnerability check, virus scanning, domain and certificate expiration check and many others, in order to make a useful product for their customers.

Different ways to monitor

The monitoring, based on the purpose, can be performed in several ways. Internal monitoring tools require some software to be installed into the monitored system, for example, corporate network. It helps to detect network issues, system performance and exclude or catch hardware and performance issues. External monitoring is performed from outside. It's purpose is check the availability and performance of the system by the third-party's eyes. Real user monitoring is external monitoring which simulates the real visitor of a site. Depending on complexity, such monitoring can analyze the page loading, content, sometimes - even design problems. Most advanced monitoring can offer its client to create a scenario for a visitor. This is called transaction monitoring and can perform some steps one-by-one: like load the page, navigate through menu, make a purchase. Passive monitoring is performed by a code which is integrated into the website code and sends specific information to the collector server each time the page is loaded. It helps to analyze customers actions on the site and analyze the traffic.

Monitoring services usually support different check protocols, and can monitor not only the websites, but also other entities like a file servers, mail servers, specific ports etc. Depending on task, monitoring interval can vary from several seconds to once per day.

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