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
"

Service is very  reliable and performs as described in sales information.  User interface is simple and easy to use.

"
- St
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 informed 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. I mean, 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
 
Stats for tasks
Sign In
Sign Up
Prices & packages
Our monitoring network
Home > Uptime reports > Stats for tasks
Report for:
Include:
Format:
Page:
Start date Hosting Dattatec
http://www.arquitecturadecasas.info/
http, 30 mins
Hosting Dattatec
http://www.deautomoviles.com.ar/
http, 30 mins
Uptime Downtime Uptime Downtime
2017-01-01 97.96 % 11 hour(s) 30 min(s) 0.11:30:31 98.93 % 6 hour(s) 39 sec(s) 0.06:00:39
2016-12-01 98.83 % 8 hour(s) 38 min(s) 0.08:38:46 99.72 % 2 hour(s) 2 min(s) 0.02:02:06
2016-11-01 96.33 % 1 day(s) 2 hour(s) 1.02:02:04 99.86 % 1 hour(s) 48 sec(s) 0.01:00:48
2016-10-01 99.86 % 1 hour(s) 3 sec(s) 0.01:00:03 100 %  
2016-09-01 99.86 % 1 hour(s) 59 sec(s) 0.01:00:59 100 % 6 sec(s) 0.00:00:06
2016-08-01 100 % 23 sec(s) 0.00:00:23 100 % 3 sec(s) 0.00:00:03
2016-07-01 100 % 27 sec(s) 0.00:00:27 100 %  
2016-06-01 100 % 30 sec(s) 0.00:00:30 99.93 % 30 min(s) 28 sec(s) 0.00:30:28
2016-05-01 100 %   99.93 % 30 min(s) 12 sec(s) 0.00:30:12
2016-04-01 100 % 10 sec(s) 0.00:00:10 100 % 25 sec(s) 0.00:00:25
2016-03-01 100 %   100 %  
2016-02-01 98.14 % 12 hour(s) 56 min(s) 0.12:56:02 97.25 % 19 hour(s) 9 min(s) 0.19:09:12
2016-01-01 99.8 % 1 hour(s) 31 min(s) 0.01:31:06 99.08 % 6 hour(s) 51 min(s) 0.06:51:14
2015-12-01 99.66 % 2 hour(s) 30 min(s) 0.02:30:15 99.73 % 2 hour(s) 56 sec(s) 0.02:00:56
2015-11-01 90.02 % 2 day(s) 23 hour(s) 2.23:41:15 85.33 % 4 day(s) 9 hour(s) 4.09:20:28
2015-10-01 73.41 % 8 day(s) 5 hour(s) 8.05:20:50 73.67 % 8 day(s) 3 hour(s) 8.03:25:45
2015-09-01 97.82 % 15 hour(s) 33 min(s) 0.15:33:52 96.15 % 1 day(s) 3 hour(s) 1.03:33:04
2015-08-01 100 % 3 sec(s) 0.00:00:03 100 % 5 sec(s) 0.00:00:05
2015-07-01 100 %   100 %  
2015-06-01 100 %   100 %  
2015-05-01 100 %   100 %  
2015-04-01 100 % 11 sec(s) 0.00:00:11 100 % 47 sec(s) 0.00:00:47
2015-03-01 100 %   100 %  
2015-02-01 100 %   100 %  
2015-01-01 100 %   100 %  
2014-12-01 100 %   100 %  
2014-11-01 100 %   100 %  
2014-10-01 100 % 8 sec(s) 0.00:00:08 100 %  
2014-09-01 100 %   100 %  
2014-08-01 100 %   100 %  
2014-07-01 100 %   100 % 21 sec(s) 0.00:00:21
2014-06-01 100 %   100 %  
2014-05-01 100 %   100 %  
2014-04-01 100 %   100 %  
2014-03-01 100 % 1 min(s) 9 sec(s) 0.00:01:09 100 % 47 sec(s) 0.00:00:47
2014-02-01 100 % 12 sec(s) 0.00:00:12 100 % 1 min(s) 16 sec(s) 0.00:01:16
2014-01-01 100 % 1 min(s) 16 sec(s) 0.00:01:16 58.94 % 9 day(s) 16 hour(s) 9.16:13:35
2013-12-01 100 %   100 %  
2013-11-01 100 % 25 sec(s) 0.00:00:25 100 % 11 sec(s) 0.00:00:11
2013-10-01 100 %   100 %  
2013-09-01 100 % 1 min(s) 56 sec(s) 0.00:01:56 100 % 1 min(s) 14 sec(s) 0.00:01:14
2013-08-01 100 % 35 sec(s) 0.00:00:35 100 % 1 min(s) 36 sec(s) 0.00:01:36
2013-07-01 99.68 % 2 hour(s) 2 min(s) 0.02:02:50 100 % 1 min(s) 4 sec(s) 0.00:01:04
2013-06-01 100 %   100 %  
2013-05-01 100 % 1 min(s) 12 sec(s) 0.00:01:12 100 %  
2013-04-01 99.91 % 35 min(s) 15 sec(s) 0.00:35:15 100 % 1 min(s) 54 sec(s) 0.00:01:54
2013-03-01 100 %   100 %  
2013-02-01 100 %   100 %  
2013-01-01 100 % 52 sec(s) 0.00:00:52 100 % 1 min(s) 1 sec(s) 0.00:01:01
2012-12-01 100 %   100 %  
2012-11-01 100 % 25 sec(s) 0.00:00:25 99.91 % 38 min(s) 10 sec(s) 0.00:38:10
2012-10-01 100 %   100 %  
2012-09-01 95.43 % 23 hour(s) 8 min(s) 0.23:08:17 99.83 % 50 min(s) 31 sec(s) 0.00:50:31
2012-08-01 100 % 1 min(s) 1 sec(s) 0.00:01:01 100 %  
2012-07-01 100 %   100 %  
2012-06-01 100 %   100 %  
2012-05-01 99.82 % 1 hour(s) 5 min(s) 0.01:05:33 99.89 % 39 min(s) 1 sec(s) 0.00:39:01
2012-04-01 100 % 1 min(s) 17 sec(s) 0.00:01:17 100 %  
2012-03-01 100 %   100 %  
2012-02-01 100 %   100 %  
2012-01-01 100 %   100 %  
2011-12-01 99.99 % 3 min(s) 14 sec(s) 0.00:03:14 99.99 % 2 min(s) 20 sec(s) 0.00:02:20
2011-11-01 100 % 1 min(s) 48 sec(s) 0.00:01:48 100 %  
2011-10-01 99.92 % 30 min(s) 23 sec(s) 0.00:30:23 100 % 56 sec(s) 0.00:00:56
2011-09-01 100 %   100 % 1 min(s) 40 sec(s) 0.00:01:40
2011-08-01 99.99 % 4 min(s) 31 sec(s) 0.00:04:31 100 % 49 sec(s) 0.00:00:49
2011-07-01 100 % 21 sec(s) 0.00:00:21 100 %  
2011-06-01 100 % 1 min(s) 43 sec(s) 0.00:01:43 100 %  
2011-05-01 100 % 1 min(s) 5 sec(s) 0.00:01:05 100 %  
2011-04-01 99.82 % 1 hour(s) 7 min(s) 0.01:07:51 100 % 1 min(s) 46 sec(s) 0.00:01:46
2011-03-01 99.99 % 4 min(s) 34 sec(s) 0.00:04:34 99.92 % 32 min(s) 46 sec(s) 0.00:32:46
2011-02-01 99.99 % 3 min(s) 54 sec(s) 0.00:03:54 100 %  
2011-01-01 100 %   99.99 % 2 min(s) 10 sec(s) 0.00:02:10
2010-12-01 100 %   100 %  
2010-11-01 99.85 % 1 hour(s) 1 min(s) 0.01:01:48 99.99 % 2 min(s) 31 sec(s) 0.00:02:31
2010-10-01 100 %   99.9 % 42 min(s) 6 sec(s) 0.00:42:06
2010-09-01 100 %   99.89 % 44 min(s) 13 sec(s) 0.00:44:13
2010-08-01 100 % 1 min(s) 51 sec(s) 0.00:01:51 99.99 % 2 min(s) 47 sec(s) 0.00:02:47
2010-07-01 99.91 % 33 min(s) 49 sec(s) 0.00:33:49 100 % 31 sec(s) 0.00:00:31
2010-06-01 100 %   100 %  
2010-05-01 100 % 25 sec(s) 0.00:00:25 100 %  
2010-04-01 100 %   100 %  
2010-03-01 99.99 % 1 min(s) 49 sec(s) 0.00:01:49 100 % 1 min(s) 6 sec(s) 0.00:01:06
2010-02-01 99.72 % 1 hour(s) 41 min(s) 0.01:41:17 99.71 % 1 hour(s) 42 min(s) 0.01:42:37
2010-01-01 100 %   98.96 % 6 hour(s) 53 min(s) 0.06:53:57
2009-12-01 95.51 % 1 day(s) 1 hour(s) 1.01:03:05 98.91 % 7 hour(s) 33 min(s) 0.07:33:06
2009-11-01 98.95 % 7 hour(s) 11 sec(s) 0.07:00:11
2009-10-01 99.14 % 5 hour(s) 46 min(s) 0.05:46:03
2009-09-01 99.83 % 1 hour(s) 2 min(s) 0.01:02:13
Share:
Send to Twitter Send to Facebook Send to LinkedIn Share on Google+
Blogs:
HostTracker blog HostTracker page on Facebook