Passive Monitoring
Passive Monitoring Passive Monitoring is the way to check the site performance by server-side software.

Passive Monitoring is the way to check the site performance by server-side software. It can create the exact copy of incoming traffic for analysis, or it can operate on real traffic. Passive monitoring may collect statistics and watch over some important values, like traffic consumption, number of visitors etc. Also it is handy to analyze the real workflow on your site. However, only server-side errors could be caught. If case of broken Іnternet connection or other Internet-related errors, passive monitoring fails - as it shows only the server performance which is Ok. You'll notice the the lack of visitors, but this fact does not appear immediately. And this is the main difference between the Passive Monitoring (server-side) and Active Monitoring (third-party).

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

This service helps me track when my website goes offline on all service platforms which are accessible (SMS, Emails and Skype) making me be aware of any issues as they occur and act instantly to make sure the customer remains happy.

"
- J.
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
Thank you for feedback!
 
Terms and Conditions
Sign In
Sign Up
Prices & packages
Our monitoring network
Home > Terms and Conditions

Limitation on Liability

  • The Company makes every effort to provide accurate and uninterrupted Service and solve all contingency problems with the Service, if these should occur. However, the Company is not responsible for incidental or consequential damages, loss of profit or any other negative consequences connected with the use of the Service

Service Suspension

  • The Company reserves the right to suspend service to a User with no explanation of the reason.

Refund

  • In case the User is not satisfied with the quality of the service provided by the Service in the current or previous month, the Company will pay back all amounts received from the User for the period in question, at his/her first request sent to the Company via e-mail.

Confidentiality of Registration Information

  • The Company does not disclose personal information provided by the User upon registration to any third parties.

Cookies

  • Cookies are employed by the Service for user identification and authentication.

Session Log

  • When a User is working with the Service Site, information about the Site pages visited by the User is being logged. This information is used to improve the functionality of the Service.
Share:
Send to Twitter Send to Facebook Send to LinkedIn Share on Google+
Blogs:
HostTracker blog HostTracker page on Facebook