Website monitoring
Website monitoring Website monitoring is an automated process of checking availability of a site.

Website monitoring is an automated process of checking availability of a site. The main goal of it is evaluation of possibility to access the site by clients. It is clear, that a site is efficient when an interested person can load the page and make a purchase or look for some information. If this action fails for some reason - the site does not execute its mission, and a client will find what he needs somewhere else.

There are many solutions of this problems, and all of them could be divided into passive and active ways. The result of monitoring is the value of uptime, measured with some accuracy. Having it, one can conclude how long is the site broken during some period of time (usually, for a year). Low uptime usually means that the server where the site is hosted, or internet connection to it, is unreliable and is required to be changed.

  • CM.Glossary.Uptime
  • CM.Glossary.Downtime
  • CM.Glossary.ActiveMonitoring
  • CM.Glossary.PassiveMonitoring
  • CM.Glossary.Availability
more glossary
"

This was very helpful for us in identifying just how dysfunctional our host was, so we changed it! 

"
- M.O.
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!
 
More
:
Home > Prices & packages
30 Days Unconditional
Moneyback Guarantee
Personal Webmaster Business Enterprise 30-Days Free Trial Free
Month
$5/mo
$14/mo
$29/mo
$99/mo
6 months
$4.50/mo
$27/6 months
$11.50/mo
$77/6 months
$69 for first 6 months
$23.17/mo
$155/6 months
$139 for first 6 months
$83.17/mo
$539/6 months
$499 for first 6 months
Year
$3.25/mo
$49/Year
$39 for first year
$9.92/mo
$149/Year
$119 for first year
$18.25/mo
$299/Year
$219 for first year
Most popular package!
$74.92/mo
$999/Year
$899 for first year
Task count 5 10 25 150 100 2
Extra task cost/month $0.70 $0.70 $0.50 $0.20 $1
Max contact count 5 10 10 2
Interval monitoring 10 mins 5 mins 1 min 1 min 1 min 30 mins
Weekly, monthly, quarterly, yearly reports + + + + + +
Monitor response time + + + + + +
Content monitoring tasks + + + + +
Custom response timeout + + + + +
Daily reports + + + + +
Maintenance scheduling + + + + +
Database monitoring tasks + + + + +
SNMP monitoring tasks + + + + +
HTTPS + + + + +
DNSBL check in task + + + +
Domain expiration monitoring in task + + + +
Certificate expiration monitoring in task + + + +
Task cron scheduling + + + +
Full log + + +
Monitor CPU, RAM, and other counters + + +
Error response snapshotting + + +
API access + +
Multiuser account + +
Free SMS credit per month ($1 = 30-50 messages) $1 $2 $5 $15 $0.50 $0