We would like to officially announce that first final version of AppBeat is ready to use! We would like to thank to all participants of our BETA version. You helped us a lot with your valuable feedback! As we promised during BETA version, we will always try to offer one of our plans for free (forever, no credit cards required). Currently we are offering five free monitors with five minute check frequency.

With our latest deployment of our core AppBeat monitoring service on two geographically separate locations, and by removing our last single point of failure (central database, which is now locally mirrored), we have achieved very robust high availability monitoring system. With this setup we are hoping for at least 99.9999% availability of our core monitoring service (web management application is separate and less critical system, it is not part of core monitoring service).

We are currently in process of deploying second instance of our AppBeat core scheduler to server on different geographic location and network. Second instance of our scheduler will be automatically activated if primary server does not respond (due to network or hardware issues). This will allow us to provide very high availability of our monitoring service for our users and customers. AppBeat was architected from beginning with high availability in mind which is very suitable for enterprise usage.

If you have less frequent monitoring and you want to check if your website or service still has errors (and you can’t wait until next scheduled run), you can click on “schedule new probe” link as shown below: This will add your monitoring request to scheduler que, and it will be automatically retested as soon as possible (usually this is in less than 10 seconds, but please note that page auto refreshes every 60 seconds - you may also manually refresh page for quicker result).

In this version of AppBeat we primarily focused on some optimizations of our core monitor service. For example, our core now sends database updates much much efficiently. In each monitoring batch that we dispatch we have several checks. When those checks return result, our dispatcher manager packs all the results into single DataTable and sends it to database as Table-Valued Parameter. This means single roundtrip to database, instead of previously tens of single database updates.