Site Click-stream Monitoring

New release: many new features and improvements (2008-08-25)

The most recent release of our site and software brings not only many improvements, but also a number of interesting new features:

• You can now restrict the monitoring of your site to a selection of our monitoring stations.
  As we are adding ever more of these stations, this has become a recurring feature request.
  How: In the [expert mode] of your rule settings, select 'Checkpoint selection'. This allows you to choose the checkpoints that will execute this rule. In case of a 'Master' sequence rule, additional checkpoints will only be used for second opinion checks. Make sure you select at least three stations for redundancy purposes.
• New IMAP and POP3 checkers now support SSL and can send 'round trip' test messages.
  These test messages are checked in the next monitoring cycle thus implementing a full round-trip email verification functionality
  How: In your rule settings for IMAP and POP3 rules select "SSL encryption". Make sure you are in [expert mode], where there will be an email address field. When an email address is found in this field, we send a test email to it in each cycle, and check for its correct delivery in the next cycle.
• New DNS checkers with many more features.
  Test for A, CNAME, MX, NS, PTR, and AAAA records and test these on our local resolvers, on your listed name servers, or on specific DNS servers. The existing dnsa and dnsns type rule will be replaced soon by this new dns type rule. How: In the [expert mode] of your rule settings type the name or IP address to be tested, select the record type, and click look-up. Now select the DNS servers that should be queried, set the other options and click save.
• In many cases, the log viewer will now also show the DNS resolve times for each check. As we move forward, we will add this for all check types.
• The web site now offers a more flexible subscription model, allowing customers to mix and match a wider range of different rule types and intervals.
• The reseller console has undergone major improvements making it easier for resellers to manage their customers' accounts.

In addition, many improvements have been made and several smaller issues have been resolved, please refer to the change log for details.

All new features are available for current and new subscribers at no extra charge. And, as always: if you are missing a feature, please let us know! We will most likely add it in a future release.

WatchMouse and Nedstat - Combining web site analytics and site performance (2008-06-02)

WatchMouse recently integrated with Nedstat's tool Sitestat. Nedstat is Europe's leading website analytics provider. Combining Nedstat's marketing intelligence with WatchMouse's website performance monitoring, enables customers to gain insight into the relationship between performance and visitor behavior.

The integration between WatchMouse and Nedstat should be of great benefit to WatchMouse customers who are using Sitestat Pro (or are considering using it) as it enables you to view your WatchMouse performance monitoring & Sitestat visitor statistics together. After making a few simple adjustments to your existing WatchMouse interface, you can view and compare both performance and visitor statistics, embedded in custom WatchMouse reports and thereby quickly spot any possible correlation between them e.g. an inverse relationship between your site's download time and your page views.

Having WatchMouse and Sitestat data presented in one custom report could help you identify when improvements to your site or infrastructure are needed, and as you implement improvements, you can track customer reaction and hopefully see a rapid return-on-investment with increased page views and online sales.

To find out how to integrate Sitestat data into your WatchMouse interface visit the Visitor statistics FAQs.

To view the brochure click here: Nedstat and WatchMouse partnership brings online marketing and technical performance data together [PDF file]

WatchMouse Public Status Pages: your own public website health page in two clicks! (2009-08-19)

Today we move the WatchMouse Public Status Pages (WMPSP) out of beta, making them available for all WatchMouse customers free of charge!

What is a Public Status Page?

A public status page is a web page that informs your customers on the status of your services, inspired by similar pages from many organisations like Amazon, Apple, Google, but also ISPs, financial institutions and other organisation who deliver critical services to other companies or the general public. Well-known examples are:

• The Amazon web services Health Dashboard
• Apple MobileMe support (top right corner)
• Google Apps Dashboard
• Nationwide (a UK bank) service page
• The WatchMouse Status Page and our Monitoring stations status (yes, we eat our own dog food)

On our Public Status Pages the current status of your selection of on-line services can be displayed, and updates (public announcements) can be placed there for your customers. The pages are hosted on the Amazon cloud infrastructure, ensuring that your status page is highly scalable. It also ensures that your status pages continue to be available even if your main site or service is not.

Should my organization have a Public Status Page?

There is a strong trend to inform customers as soon as possible when certain services become unavailable, and announce maintenance well in advance. If you would like to provide your customers a dedicated status page for the on-line services you provide to them, WMPSP is a very efficient and cost-effective solution for your organisation. You can have a Public Status Page set up in minutes by creating one or more rules in your WatchMouse account, set up a public folder, and move these rules into this folder. Using the WMPSP setting page you can post announcements, annotate current issues, and optionally set up a special host name (CNAME) so people can access the status page using your domain name, e.g. status.yourdomain.com.

How does it work?

After you have set up a public folder with monitoring rules in your account, the status of these rules will be pushed to http://status.watchmouse.com/NNN automatically (where NNN is a unique id for your status page). Make sure the settings of the rules, and especially the timers for the performance thresholds are according to your standards / SLA. You may want to have a similar set of rules with more strict thresholds for internal use so you will get notified well before your Public Status Page is update. Note that you can have your own host name as well, i.e.status.yourdomain.com instead of http://status.watchmouse.com/NNN

Whenever there is a performance or availability issue, you can annotate this in your WatchMouse account and this information (e.g. "our technicians are working on a solution, expected to be available at 16:00") will be pushed to the WMPSP as well. Similarly, you can announce maintenance or downtime in the same procedure and this will be listed in the announcement section of your Public Status Page.

All Public Status Page are hosted on the Amazon web services infrastructure, making it independent from your own servers availability and ensuring a very high availability and scalability.

Get started now!

• Login into your account and go to the standard rule settings page
• Create a new rule folder for each WMPSP you would like to set up, and create rules within those folder that are representative for the availability of your main services.
• Go to the WMPSP setting page and click the [add] button, and select a folder you created in the previous step.
• Optionally you can also add a host name within your own domain in the CNAME field. Not that you have to add a CNAME record to you DNS for this host name pointing to status.watchmouse.com.
• Click [make public] and you're done! Note that it might take a minute or two before the status page is actually available, since the data has to be transferred to the Amazon AWS platform first.
• Test your WMPSP by clicking on the Name and/or CNAME links in the public folder listing. Observe that each rule has it's own detail page which looks like this: WMPSP for the WatchMouse web site
• Note that the name and logo shown can be changed in your account details
• Next you can add announcements to your WMPSP in case you have scheduled maintenance for one of more services or when actual issues arise and you would like to update your customers about the progress fixing it.

WatchMouse Urges AdWords Advertisers To Act Swiftly To Avoid Costly Mistakes (2008-04-08)

Utrecht, The Netherlands, 12th March 2008, Research has long confirmed that slow websites drive away potential customers. As Google announces changes to the way they score their immensely popular AdWords, it also appears that sites with slow landing pages create issues for online advertising.

Google will soon incorporate landing page load time (the amount of time it takes for a page to show after a user clicks an ad) as an additional factor in determining a site’s ‘quality score.’ Google says they are making this change as “users value ads that bring them to the information they want as efficiently as possible.” Experts warn that failure to demonstrate a fast load time will result in your keywords getting a lower quality score and higher minimum bids.

A post by Google on the WebMasterWorld blog indicates that the new scoring method will be announced shortly, "now that the (landing) page load time initiative has been mentioned in this and other public forums, the Inside AdWords blog post is likely to be posted sooner rather than later - perhaps as early as this week".

The impact of the new AdWords scoring method will be financial. WatchMouse CTO, Mark Pors, advised "when Google introduces the new scoring method, AdWords with slow landing pages will cost more. Slow landing pages will be listed below their faster competitors, thus increasing the cost-per-click (CPC) to get a higher position, or substantially lowering the number of customers visiting the site, as studies show that the top few AdWords obtain the vast majority of the traffic volume". Pors suggested “businesses should do everything possible to prevent a low Google 'quality score' and do so as soon as possible, as the AdWord system will only re-evaluate landing pages on a monthly basis”.

Measuring web site performance, however, is not a straightforward exercise, as many factors influence it. Pors urges Google AdWords customers to “avoid costly mistakes and have independent website monitoring set up to continuously measure load time from different locations worldwide. Once a business has accurate statistics, it can make necessary changes well in advance of Google’s new ’Quality Score’ launch date, and keep a close eye on it after that”.

About WatchMouse

Accurate and independent monitoring of website performance enables businesses to address load time and many other potential user experience issues which might not be apparent when conducting in-house or single point monitoring. WatchMouse’s global infrastructure provides its customers with peace of mind that their site has been tested from the user’s perspective, and external to the organization. As industry leader in website performance monitoring, WatchMouse offers customers a web-based service with features such as SMS/email alerting and extensive reporting. Many of the world’s lead brands depend on WatchMouse to monitor their sites, providing independent confirmation of both in-house and suppliers’ website performance.

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.

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