Today we published AppBeat 1.3.0 which implements support for third-party notification providers (from Account / Integrations). We are also happy to announce that first provider to be implemented in AppBeat is PagerDuty (available to all users, even those on Free Plan). You can add PagerDuty to your AppBeat account by following these easy steps: click “Account / Integrations”: click on “PagerDuty” button to add new notification channel (you can add multiple PagerDuty notification types; ServiceKey can be obtained on your PagerDuty website): once you have tested and added your PagerDuty notification please click on “Services & Checks”.

We are currently working on version of AppBeat which will have support for PagerDuty (third party incident management tool). Their API is very easy to use. Here is code example from AppBeat which sends PagerDuty notifications: namespace AppBeat.Core.Notifications { class PagerDuty { //NOTE: this is dispatched in separate thread, exception handling is done by NotificationManager public static bool Send(ThirdPartyDispatcher.CustomNotification notification) { var settings = (Types.CustomNotificationPagerDuty)notification.Settings; if (string.IsNullOrWhiteSpace(settings.ServiceKey)) { throw new Exception("ServiceKey is required!

Update on May 17th, 2020: please visit synthetic-testing.com for newest information about our synthetic testing Today we published first public preview version of transaction monitoring and it is available from “Automated Web Testing” module. Similar feature is also offered by Ghost Inspector and Pingdom. Please note that this AppBeat functionality is not yet complete (you can’t currently save tests or schedule periodic monitoring). If you don’t have AppBeat account you can sign up here for free.

Our AppBeat application monitor was recently mentioned in article Top 15 Website Monitoring Tools. Free version of our app is available for everyone and you can sign-up here. Our long-term goal is high - to become most reliable, friendly and affordable monitoring solution on market (and from feedback we receive from our users, we think we are on the right track!).

We have successfully completed deployment of AppBeat 1.1 Our paid users should now have option to select preferred test location (Account / Check settings), where free users have only “Random location” option. Similar functionality is also provided by Pingdom and StatusCake. Everyone can also fine-tune “Number of confirmation checks” option which defines behaviour when your check does not return positive result. By default we try to confirm failure by two additional confirmation checks from different geographic locations and networks.