Web Site Monitoring

New web site monitoring station: Copenhagen, Denmark (2007-09-08)

The WatchMouse network of monitoring stations expands again, this time in Copenhagen, a another site monitoring station in Scandinavia, bringing the total number of checkpoints to 23.

The new checkpoint will appear automatically in your logs. You can also set one of the new checkpoints as the primary checkpoint in your monitoring settings.

The current status of the WatchMouse web site monitoring network can be found on the 'About' tab of the WatchMouse site.

New web site monitoring station: Melbourne, Australia (2007-05-29)

The WatchMouse network of monitoring stations expands again, this time in Melbourne, a second web site monitoring station in Australia, bringing the total number of checkpoints to 21.

The new checkpoint will appear automatically in your logs. You can also set one of the new checkpoints as the primary checkpoint in your monitoring settings.

The current status of the WatchMouse web site monitoring network can be found on the 'About' tab of the WatchMouse site.

New Monitoring Stations in Belgium, Ireland, Norway and Mexico (2009-04-26)

The WatchMouse performance monitoring network expands with another four stations, this time in:

• Antwerp, Belgium
• Dublin, Ireland
• Oslo, Norway
• Guadalajara, Mexico

The total number of monitoring stations is now 39, and follows customer demand in these countries, as well as demands from companies operating sites that cater to a worldwide audience.

The new monitoring stations will appear automatically in the customer dashboard logs when monitoring is performed from random locations. Customers can select the new locations as the primary monitoring station in the monitoring settings.

The current status of the WatchMouse web site monitoring network can be found in the 'About' tab on the WatchMouse site.

"Want to know the performance of your website?" (2006-11-29)

- WatchMouse launches Site Monitor for PC users –

Netherlands, November 29, 2006 - WatchMouse launches its free WatchMouse Site Monitor for Windows. This application provides PC users insight into the availability of their website(s) at all times. The Site Monitor can be downloaded for free at the WatchMouse website. Installing it only takes a minute.

The Site Monitor checks your company's site or your personal website at fixed intervals (5, 15, 30 or 60 minutes) from your own pc. When an error is found, or after 2 to 5 consecutive errors, you are alerted and the error is verified by all WatchMouse monitoring stations. Also, the availability of the site in the last 72 hours is shown in a performance chart.

The Site Monitor can be combined with a free WatchMouse account. This gives you the following extra benefits:

• The application can show you the monitoring results of all websites included in the account
• The monitoring is not only done from your own PC, but also from more than 20 WatchMouse checkpoints worldwide
• The application shows performance charts for any period in the Site Monitor
• In case of an alert the WatchMouse site is launched for more details
• Monitoring continues even when the PC is without an internet connection

In exchange for these extra benefits WatchMouse asks you to place a small uptime banner on the sites that are monitored.

The WatchMouse Site Monitor for Windows can be downloaded for free at http://www.watchmouse.com/windows/site_monitor.php Installing it only takes a minute.

WatchMouse expands Website Monitoring Infrastructure to 35 Global Monitoring Stations (2008-09-01)

In order to meet customer demand, WatchMouse is proud to announce the expansion of its global infrastructure with another eight monitoring stations being deployed over the past two months. The new stations are in: India, Israel, Japan, New Zealand, Russia, South Africa, Switzerland and the USA. WatchMouse now offers 25 monitoring stations in major European and North American cities, with a further 10 stations spread across Africa, the Middle East, South America and Oceania.

WatchMouse's extensive infrastructure provides the means to accurately monitor sites and web applications from the perspective of users based in different global locations. Such multi-point monitoring is imperative as site performance varies greatly depending on the location of the user (e.g. customers in the USA might quickly access a site, while for users in Germany, the same site has errors or a long load time). WatchMouse CTO, Mark Pors explains that "Even if your site works well from your headquarters, customers may still have trouble reaching it from different external locations. As a slow or faulty site can frustrate users, damage the reputation of a company and result in lost sales, it is essential to monitor from more than one point."

As the vast majority of businesses are aware of the need for global performance monitoring, WatchMouse was surprised to find global performance issues on the sites of some major international organizations, including the social networking site Facebook. In recent research WatchMouse found that facebook.com performs well in the USA but showed serious user issues from many other locations.

WatchMouse’s market leading infrastructure can help international organizations identify performance issues. Equally, WatchMouse supports clients who require performance monitoring within a particular region by allowing monitoring to be restricted to a sub-set of monitoring stations. This feature is useful for companies that only trade within a large country (e.g. USA) or region (e.g. Europe) but still require comprehensive monitoring within their area of operation.

About WatchMouse

WatchMouse provides global performance monitoring to thousands of customers in over 70 countries. In addition to a market leading infrastructure, WatchMouse offers automated alerting and an advanced user interface for complete self-management of all monitoring features and subscription details.

WatchMouse releases new Site Performance Monitoring Widget for Apple users (download widget) (2006-10-22)

WatchMouse releases 2.0 widget for dashboard, aimed at Internet site performance monitoring.

NETHERLANDS, 2006-10-23. By means of the widget Apple users can get direct insight into the performance of their own Internet site. The widget can be downloaded for free from the Apple website.

In 2002, WatchMouse (www.watchmouse.com) introduced a new concept for Internet site monitoring. By means of ongoing simulation of Internet visitors the performance of sites and servers is verified. If a site is not responding, an alert message is sent immediately through SMS, pager, Instant Messenger or e-mail. The sites are checked from over twenty monitoring stations worldwide. This is done 24 hours per day, seven days per week. The service is completely web based: customers don't have to install software, everything is 100% self-service, which keeps the costs low.

The three founders of WatchMouse, Niels Eijsbroek, Stan van de Burgt and Mark Pors are enormous Mac-fans with a total of twenty Macs in their possession. The monitoring widget is quite unique: it is a combination of a desktop and a hosted application. When the widgets detects a problem with the site it is checking, it alerts the user with a 'beep', followed by the launch of a web browser, which is directed to a web application on watchmouse.com. There the site is checked from over 20 different locations worldwide.

Worldwide monitoring

The new version (2.0.4) brings continuous performance monitoring, even when the Mac is not connected to the Internet, by connecting the widget to a WatchMouse account (free or paid). In October 2005, WatchMouse released the first version of this widget, which was downloaded over 10.000 times.

WatchMouse has made the widget available free of charge "because we have become addicted to it, ever since we started using the first beta version of the widget", says creative director Niels Eijsbroek. "We give the widget away for free mainly for the fun part. And of course it's also important to bring site performance monitoring to the attention of our fellow Apple-users."

The free WatchMouse site monitoring widget can be downloaded from the Apple website:

http://www.apple.com/downloads/dashboard/networking_security/watchmousesitemonitor.html

About WatchMouse

Companies can easily monitor their own Internet sites using WatchMouse's monitoring service. WatchMouse has been monitoring Internet sites and e-commerce applications for companies throughout the world since 2002. WatchMouse has thousands of customers in more than 70 countries. The services supplied by WatchMouse are available in nine languages, and analysis are performed from various locations and over numerous networks, using a world-wide monitoring network.

In 2005, WatchMouse was voted a Deloitte Rising Star in the Netherlands, as part of the Fast 50 awards; the list of the 50 fastest growing technology companies.

Further information can be found at: www.watchmouse.com

I'm sending you this e-mail just to say how very impressed I am with your site and services. (2010-01-13)

I'm sending you this e-mail just to say how very impressed I am with your site and services. I found your site on Google and spent a long time comparing you to the other site monitoring services that are out there. Your site definitely was the most appealing of them all and consequently I signed up for the silver package today.

Simon Bland, ProWeb Design

Website performance is the key to customer satisfaction (2007-06-27)

How often have you typed in the Google URL and received a page that will not load? I am willing to bet that this is a rare occurrence. Despite its busy traffic, Google is a textbook example of a web site that has almost perfect performance and therefore serves a great number of satisfied customers. The market share of the search engine is a resounding confirmation of this. You are assisted quickly, so you come back sooner. Research conducted by JupiterResearch has revealed that visitors to a site only have 4 seconds of patience. If the site has not been loaded by that time, they leave. Error messages also prompt potential customers to go to the competition.

Why do organisations still devote so little attention to the effective availability of their site? Performance is the key to satisfied customers. For many companies, their web site is the face of the organisation. Consumers and also business users of the Internet use the wealth of information on the web to compare purchasing options. It is of immeasurable importance that they are also actually able to find what they are looking for. If this is not possible at one company, competitors are straining at the leash to offer their services through a correctly functioning site.

Coming back to the praise that we had for Google, we see that the search engine has made significant investments in the availability of its web site. The page is run by several machines at various sites. If one crashes there are enough back-up servers that can take over the traffic flows to guarantee optimum performance. In addition, the search machine invests a great deal of time and money in the right hardware and people. Although the site has a difficult task – searching through an index of billions of documents – it is almost always available and loads fast.

The actual site is unspectacular in construction. This applies to the majority of sites with a high level of availability. Simple sites such as the news site NU.nl are almost always easy to access. Nevertheless, it is not only the layout of the site that determines how the web page performs. Too many photos, long symbols and frills make web sites slower to respond. The fact that the ‘back end’ of the site is not efficiently programmed also contributes to longer loading times. Frequent consultation of background databases is also detrimental to the speed of the page.

Where it often goes wrong is when different people are working on a site, thereby disturbing the links between the various elements. The different parts of the site will work correctly, but the site as a whole will fail to perform. This means long waiting times for people who want to use the services of a company.

Service providers at the upper end of the market are becoming increasingly aware of this. The contracts that they use frequently include a service level agreement (SLA) for the part for which they are responsible. Nevertheless, they regularly make mistakes due to the fact that the promised performance is not subsequently verified (by an independent party). Although it is now essentially part of the contract, there is insufficient actual verification. Ideally, web site performance should become a permanent component of a contract. In addition, clear internal agreements must be made on who has final responsibility for the efficient loading and availability of a site.

Regular testing is also essential for the facilitation of good availability. This will prevent a great deal of errors, keeping the site up and running at crucial times. The storm that blew over the Netherlands at the end of January was a good opportunity to see which sites were prepared for extreme loads and which were not. The site of the Dutch weather institute, KNMI, was almost unreachable, while some logical thought could have protected them from this eventuality. If you know that a major storm is heading towards the country you can be sure that people will search for information on the weather and roads on the Internet. Sites such as those of KLM and Schiphol were also unreachable, while the specially created site Crisis.nl, which had been kept as simple as possible, was able to serve a large number of people.

Including ‘stress tests’ in a SLA or conducting them regularly in-house is therefore to be recommended. Companies can easily take control by ensuring that their service provider executes this type of test or by putting their own site under pressure. This is the best method of checking whether your web site can handle a sudden increase in visitor numbers. It is also good to know whether the servers on which your site is running actually ensure that your page is always available and loads correctly. For companies, it is crucial to see when they are off air. This can save them a large amount of money every year and will also reduce the number of irritated visitors to the site. This is how you keep customers satisfied and keep the company running.

Mark Pors
Chief Technology Officer at WatchMouse

WatchMouse provides site performance monitoring and stress test services

What do you want to check with a service such as Watchmouse? (2005-01-31)

As I explained in my previous column, you can use a monitoring service in a number of roles. Common to all these roles is the fact that you are keeping alive some services for the benefit of your customers, suppliers, employees or partners. These users are, in the end, all that counts.

What are the objects that you should be checking? Obviously, the least you want to do is check the service that is most visible to these users. This could be the webserver, or a POP or FTP server for example. You would start by setting up a rule to check the server and a URL. The frequency with which you can monitor (that is: the elapsed time between checks) is typically limited by the type of subscription that you have. Only in specific cases would you not check as often as your subscription allows.

Note that there is a difference between a CONNECT on port 80 rule and a HTTP rule. The first just connects to the port that the webserver is supposed to use. The HTTP rule also checks whether the webserver can produce a valid HTTP response, and whether the document can be found. You probably want the latter check.
Similar reasoning applies to POP and FTP checks. If you set up two different rules on the same host, this allows you to distinguish for example between a broken webserver and a host that is down. If you want even more content oriented checks, have a look at the so-called PLUG-IN rules. Additionally, you can set up checks to make sure that your users are actually using the services that you intend them to. The whole Internet depends heavily on the domain name system(DNS) functioning correctly. If it does not work properly your users may be directed to another site than you intended. This could be a configuration error, but it could also be a defamation hack. In either case, you want to know.
First of all you want to check whether the root servers of the Internet accurately find the DNS that is serving you. This can be checked with a DNSNS rule. What you are checking with this rule is whether the registrar's databases are correct. Second, you want to check if that DNS server (and its slaves) are serving up the proper IP address for the server. For this you can use the DNSA rule, and it will warn you if the DNS server is not working or serves up the wrong address. (Note that the hosting party can change that address at its discretion, as part of a renumbering operation for example.)

Who should you notify of rule failures? Again, different roles have different information requirements. You want to notify the person who can fix things as soon as possible. Mail or SMS/text them directly, you do not want to be in the loop. You might set up an escalation chain, which fires off after a certain amount of errors. Note: make sure that you send the message on a channel that is not affected by the outage: if your e-mail system does not work, delivering a message to that effect should not depend on that e-mail system.
The people in charge of overseeing somebody else's service levels should only get escalation messages, if at all. Rather, they should get the weekly or monthly service reports.

Peter van Eijk is a management consultant specialized in management of network infrastructures. He can be reached via his contact page.

Linksys WVC54GCA Wireless-G Multiple Cross Site Scripting Vulnerabilities (2009-04-28)

Linksys WVC54GCA Wireless-G Internet Home Monitoring Camera is prone to multiple cross-site scripting vulnerabilities because the software fails to sufficiently sanitize user-supplied data.

An attacker may leverage these issues to execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. This may allow the attacker to steal cookie-based authentication credentials and to launch other attacks.

Linksys WVC54GCA Wireless-G Internet Home Monitoring Camera firmware 1.00R22 and 1.00R24 are affected; other versions may also be vulnerable.

Just For Fun Network Management and Monitoring System Multiple Remote Vulnerabilities (2007-06-12)

Just For Fun Network Management and Monitoring System (JFFNMS) is prone to multiple remote vulnerabilities, including a cross-site scripting issue, an SQL-injection issue, and multiple information-disclosure issues.

An attacker can exploit these issues by manipulating the SQL query logic to carry out unauthorized actions on the underlying database, access sensitive information, and obtain cookie-based authentication credentials.

These issues affect versions prior to JFFNMS 0.8.4-pre3.

Euro 2008 losers are actually web site winners. (2010-01-13)

France may have left Euro 2008 with its tail between its legs after a humiliating defeat by Italy, but the country still topped the league when it came to having the best sporting web site. For what little consolation that brings.

WatchMouse, a website performance monitoring outfit, carried out its own nailbiting tournament to find the Euro 2008 nation with the best sport website by fashioning an index which takes into account three parameters; errors, speed (load time) and availability.

4 New APIs: Wine, Whois and Website Monitoring (2010-01-13)

WatchMouse API: The WatchMouse service checks the behavior and availability of websites. WatchMouse "allows site owners to optimize the internet experience of their customers. A worldwide network checks websites from 40 different locations in 25 countries around the globe."

Facebook tops one list of 'slow and inaccessible' social networks (2010-01-13)

On Thursday, Web site-monitoring firm WatchMouse released the results of a study about the performance of 104 social-media sites--social networks, blogging communities, bookmarking sites, and the like--and boldly deemed them to be overall "slow and inaccessible."

Test phase Frankfurt checkpoint (2005-03-29)

As you may have noticed in your logs, we are slowly introducing a new monitoring station in Frankfurt, Germany. Not all protocols are serviced at this checkpoint yet..., and we use in about 5% of the checks.

Keep an I on this blog, and on the official news section of our site for the formal announcement!

New features: POSTing forms and Read limit (2005-03-28)

Today, we released the new monitoring software to our checkpoints. New features:

• Post form fields to a webserver (both in http and match rules)
• Limit the number of bytes read. Relevant for checking very large pages or streams

The site will be updated within days. Look at the settings page after logging in.

WatchMouse 1.4.26 API deployed (2008-02-24)

Today, a minor release of the WatchMouse 1.4 API was deployed on http://api.watchmouse.com/1.4/. The current version is now 1.4.26. The changes are backward compatible with the previous version.

Changes w.r.t. 1.4.25

• self-documenting calls, add ?doc after the call, no other parameters and the parameter specification is shown (try and click the URL above!)
• new parameter 'acct' (account) on all rule, contact, and folder calls so
  1. resellers and other accounts with sub accounts can login with their own credentials and then access the sub-account
  2. accounts with read access rights to other accounts can access these accounts (graphs, logs)
• alternative output formats for logs (Excell, tab delimited, CSV, streaming)
• new calls added:
  • info_cps - get information on checkpoints (monitoring stations)
  • info_ip - get information about a given host (or about caller)
  • info_country (beta) - get information about a given country
  • info_currency (beta) - get information about a given currency
  • fldr_add/mod/get/del - manipulate rule folders
  • rule_check - check a rule now
  • ch_add/mod/get/del - manipulate contacts
  • acct_new/add - calls to create additional accounts
• version in XML output (first enclosing tag)
• no IP check on acct_whois call (used for auto login on WatchMouse site)
• use API password instead of account password if present (not supported on the WatchMouse site yet)
• full support for tags in rule_add/mod/get/del and rule_graph now
• support PNGs as error message for rule_graph so developper can always show a picture
• use ip geo information if applicable