Monitoring System

New Service: Monitoring the epicenter (DNS) of your online brands (2008-01-24)

Your domain name directs customers to a website where you represent your brand and all that it stands for but are you managing and regularly monitoring the domain name service (DNS) which translates your domain name and brings your customers to you? DNS consistency monitoring can help ensure your business does not lose customers to a slow or faulty DNS.

It is useless to have paid for an expensive and fully redundant web site server (park), if the DNS servers fail to respond, respond incorrectly, or inconsistently. Your DNS must be consistent and correct. Monitoring for DNS consistency is particularly important if you have online services relying on one or more domain names (and that is almost always the case). It doesn't matter if your DNS servers are maintained in-house or outsourced, you need to know if they are doing what they are supposed to do. WatchMouse's DNS consistency monitoring (now available in closed beta) checks your DNS systems and provides rapid notification of any unexpected DNS behaviour.

The WatchMouse's 'domain' type rule allows you to monitor the consistency of the behaviour of your DNS servers. It queries for a specified domain, performs a number of checks to test the health of your DNS servers and monitors for any difference in behaviour of your name servers. (If you also need to check that a domain name resolves to the correct IP address(es), you can use the 'dns' type rule which will be offered as part of the WatchMouse DNS consistency monitoring).

This new service will be available to all WatchMouse customers with a performance monitoring subscription (Webmaster and higher) and can be configured on the Monitoring Settings page. To set-up DNS consistency monitoring, simply enter the domain name (advanced settings are available).

Fancy participating in our closed beta test?

• Contact us to request participation in the beta.
• Collect all the domain names that are important to your business.
• Go to the Monitoring Settings page.
• Add a 'new rule' and select 'domain' from the type menu, for each of the domains you wish to monitor.
• Specify the other settings you would like for other rule types, hit 'save', and you're done!
• The results of the domain name monitoring appear in your logs, reports, and graphs instantly.

BadBoy Software updates scripting recorder to improve WatchMouse's Functional testing service (2009-01-07)

The WatchMouse Functional testing service allows you to define multi-step tests through a website and replay them periodically from the WatchMouse monitoring stations. This goes beyond just monitoring site performance and uptime, it allows you to verify that your web applications and back end systems really work.
More information on this service can be found on the Transaction Monitoring & Web Application Testing page.

In a co-operation with BadBoy software, who provide a tailored version of their recoder software which allows you to upload the resulting script directly into your WatchMouse dashboard.

Feedback from our "Functional testing" customers has lead to several essential improvements to the BadBoy recorder. This improved version has now been released and we recommend all our customers to upgrade to this version.
The new - WatchMouse specific - version can be downloaded here: http://www.badboy.com.au/versions/BadboyInstaller-2.0-latest_wm.exe

The most important changes are:

CHANGES IN BADBOY 2.0.7

   #1097: Multipart Forms Incorrectly export Parameters to JMeter Encoded causing Double Encoding

   #1087: Use Follow-Redirect Option in JMeter for More Reliable Export Playback

   #1086: Export Referer and Other Default Headers to JMeter

   #1085: Assertions placed as Children of Requests not Exported to JMeter

CHANGES IN BADBOY 2.0.6.1

   #1075: Security Update (MS08-052 - Critical)

The full release notes can be found here: http://badboy.com.au/versions/ReleaseNotes-2.0.7.txt

Monitor your transition to IPv6 with WatchMouse (2009-10-14)

You've heard it before, and it's being announced more frequently and louder: The number of available addresses on the Internet is running out, and we all should move to the new addressing scheme, IPv6, as soon as possible. The uptake has been rather slow in the past, but that seems to be changing now as companies, ISPs, and other organizations are taking their first steps on the road to the IPv6 world. For most of these companies, however, this is quite a big step, with many things to consider and many uncertainties.

External IPv6 monitoring

As of today, WatchMouse offers IPv6 monitoring for web sites and other external services of your company. The monitoring network will, just like visitors of your website that happen to be on an IPv6 connected network, connect to your site when an IPv6 record is available in the DNS of your domain.

Check your IPv6 connectivity right now? Just visit our Check Host tool or the Ping tool. And while you're at it, set up a rule in your account to monitor your site continuously from our world wide monitoring network.

Many changes

To fully enable IPv6 monitoring, we have upgraded several components of our infrastructure:

• Our worldwide monitoring infrastructure, including the monitoring software
• The backend systems, including our databases and the WatchMouse API (see a post on this on WatchMouse Labs).
• The configuration portal (settings), where you can now specify whether or not to monitor over IPv6, if possible.
• The free tools on our site: check host and ping.

By offering IPv6 standard in all packages (including the free package and the 30-day trial) and in the tools on our site, we hope to facilitate a smoother transition to IPv6 in your organization.

Is your company interested in IPv6? Then do keep an eye on our IPv6 posts on WatchMouse labs.

LB Icon chooses WatchMouse for independent website monitoring (2005-01-31)

Customer websites verified from the visitors' perspective

LB Icon and WatchMouse have signed a contract for the continuous monitoring of the websites and services of LB Icons' customers. Using the WatchMouse services, LB Icon expects to raise its service level even higher.

The Application Management & Hosting Services (AM&HS) group of LB Icon maintains the administration and management of servers and applications of a large number of (international) clients. This makes AM&HS responsible for the performance and availability of the websites and Internet applications.

Using the WatchMouse services, AM&HS will instantly be aware of upcoming and/or acute incidents related to the websites of its clients, and can, as a result, resolve problems in a short time frame.
The websites and their functionality are checked for accessibility, speed and conformance from different locations around the world. Because the websites are checked in the same way that visitors are experiencing them, incidents will be detected at an early stage. Also, using WatchMouse's objective periodical reports, it is possible to see if the performance is in accordance with the agreed service levels (SLAs).

Eveline Aendekerk, MD a.i.: "The door of a shop should never be jammed, websites and the functionality on those sites should simply be accessible and available. Our clients should be able to rely on this completely, so they can focus on their primary business processes, such as communication, interaction and sales.
We chose WatchMouse because of their expertise, and also because of the simplicity and user-friendliness of their system and services".

Stan P. van de Burgt, one of the founders of WatchMouse: "I find it a powerful gesture that LB Icon doesn't just monitor the websites of their clients, but that they selected an external party for this, and on top of that give their clients access to the results. Many companies where the website plays an essential role in business, don't have any awareness of this. They have no idea of the risks and the resulting damage, until the day comes that things actually go wrong"

About Lost Boys

For 11 years Lost Boys has been a major service provider in the area of (mobile) Internet. Lost Boys offers a combination of strategy, design, technical development, implementation, application management and hosting of Internet- and mobile solutions. The Amsterdam based corporation is part of the Lost Boys/IconMedialab Group and is listed on the Stockholm Stock Exchange and Euronext Amsterdam. Lost Boys operates with 600 employees in 7 countries, both in Europe and the United States.

http://www.lostboys.nl/
http://iconmedialab.com/

About WatchMouse

WatchMouse is a service of RoundZero. Since 2001, WatchMouse has been checking Internet sites and e-commerce applications of major companies all over the world. The WatchMouse services are available in 8 languages and analysis is performed through its worldwide monitoring network at different locations and networks. WatchMouse has thousands of users in more than 70 countries.

http://www.watchmouse.com/

Linux-based website beats Windows-based sites (2007-06-24)

WatchMouse research shows Linux/Apache has less downtime and yields faster websites than Microsoft/IIS

London, June 20, 2007 – Linux websites have better uptime and load faster than Windows-based websites. Research by WatchMouse, a website monitoring company, also shows that web server platform Apache outperforms the Microsoft IIS platform. Therefore, having a Linux website and an Apache webserver platform offers the best choice for professional web pages.

WatchMouse researched the performance of over 1500 websites across different economic sectors in Europe. Most websites in this study are based on either Linux or Windows. Linux offers the best uptime. When looking at web server platforms the overall opinion favours Microsoft IIS and Apache although the latter outperforms the former in this area as well. The research finds that apart from operating system and web server platform, uptime also depends on the country where the server is based.

On average, Windows and Linux are running more than three quarters of all websites. However, there are differences between countries. Poland and Germany favour Linux combined with Apache for their websites while the professional sites in the UK and Sweden rely heavily on Windows/ Microsoft IIS. When looking at the relative performance of the different web server platforms, Linux clearly beats Windows.

One in four of the monitored professional websites have an uptime of 99.9% which suffices for customer satisfaction. Two thirds of the websites have an availability of less than 99.9% which accounts for at least 8 hours downtime per year. According to WatchMouse this is not acceptable.

“Even though the companies in our study seem to prefer Windows over Linux, our research shows they would be better off using Linux/Apache based websites. Research has shown that most web users are very impatient and will wait no longer than four seconds for a webpage to load”, says Mark Pors, Chief Technology Officer at WatchMouse. “Companies need to realise that website uptime is crucial for a healthy customer satisfaction and a solid client base. Organisations need to become more aware of the impact the choice of web server platform can have on their overall availability and performance.”

A complete overview of the monitoring results of the WatchMouse Site Availability Index, listing all the sites monitored, can be found on http://www.watchmouse.com/SPI/

WatchMouse Launches API-status.com (2010-01-20)

New Site Monitors and Measures Uptime of 26 Popular API and Cloud Services Websites; Report Reveals Amazon, Google and Yahoo Among the Best and Vimeo, foursquare and Yammer Among the Worst Performers

WatchMouse, a global industry leader in self-service website and application performance monitoring, announced the launch today of API-status.com, a new dedicated website for monitoring and measuring the real time availability and performance of the public APIs of 26 heavily trafficked, popular “cloud computing” mega web services including: Google Search, Google Maps, Bing, Facebook, Twitter, SalesForce, YouTube, Amazon, eBay, PayPal, Wikipedia and others.

API-status.com does a call and check for a valid result on each of the APIs, and if the result is wrong or is received after four seconds, it is noted as an error and unavailable. The percentage of availability or uptime is based on the number of errors reported; details on API-status.com include a seven-day history along with a 24-hour glance and performance indication by country.

"Nearly all websites nowadays include information from outside sources such as maps or social media feeds. It impacts millions of websites worldwide if these services and systems are slow or down and can invoke a global domino effect of breakages and slowness," states Mark Pors, CTO and co-founder of WatchMouse. "The four-second limit on the response time may seem strict, but it is actually a long time, especially when the (mash-up) sites need to do multiple API calls to present a complete page to the visitor."

According to a recent report produced by Forrester Research and Akamai, two seconds was revealed as the new threshold of acceptability for e-commerce web page response times.

30-Day Report Card and Methodology

WatchMouse monitored the availability of 26 API/cloud web services during the period of December 16, 2009 to January 16, 2010. The results found that Yammer API had the lowest availability with 96.06 percent uptime and Amazon, Google Maps, Google Search, last.fm, and Yahoo Maps with the highest availability with 100 percent uptime. In accordance with industry standards, availability of greater than or equal to 99.9 percent is regarded as "good" while anything below 99 percent is regarded as "poor" site uptime. The methodology for testing the sites includes one simple API call and check for a valid result. This typically means an authentication action for most APIs, including a login, followed by a search or listing action, plus a check of the expected result action. The expected result can immediately return as an error or if the expected result action is reported after four seconds, it is also logged as an error. These errors are used to create the percentage of availability or uptime for each of the sites. Each site is checked in real time using the WatchMouse Public Status Pages tool, which can be used to measure and report the availability of any public website. Companies use the tool, which is hosted on the Amazon platform to inform customers and report publicly on the status of their services.

Click here to read the full report of all 26 website services uptime or visit www.API-status.com for real time status and statistical data on each website.

About APIs

An application programming interface (API) is a set of data structures, protocols, routines and tools for accessing a web-based software application. The practice of publishing APIs allows web communities to create an open architecture for sharing content and data between communities and applications. Content that is created in one place can then be dynamically retreived, posted and/or updated in multiple locations on the Web.

About WatchMouse

Founded in 2002, WatchMouse is a global industry leader in self-service website and application performance monitoring. WatchMouse product tests the behavior and availability of websites, services and applications utilizing an infrastructure that includes 42 worldwide remote monitoring stations in 26 countries. Advanced remote monitoring helps eliminate website downtime, allows issues to be identified and resolved quickly and guarantees peace of mind that your website has been thoroughly and externally tested from the user’s perspective. WatchMouse’s web-based products are easily deployed and offer many features including: extensive reporting tools, root cause analysis, automated email and text/SMS alerts. WatchMouse supports Philips, ING, VeriSign and other leading global companies who depend on WatchMouse to provide independent confirmation of both in-house and suppliers’ website performance. WatchMouse is a privately held company headquartered in Utrecht, The Netherlands. Learn more at http://www.watchmouse.com.

We guarantee our customers 100% uptime. (2010-01-13)

We guarantee our customers 100% uptime. To fulfill this guarantee, we use several monitoring systems.
Based on our experiences we can say: WatchMouse is REALLY reliable!

Gerwin Scheeve, Lost Boys

WatchMouse Periodic Vulnerability Scanning has enabled us... (2010-01-13)

WatchMouse Periodic Vulnerability Scanning has enabled us to overcome the time consuming task of managing monitoring internally. The removal of all duplicate findings and neat presentation in the WatchMouse Customer Console further reduces the time Lectric Webservices has to spend on maintaining secure systems.

General Manager, LECTRIC Webservices

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.

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.