AppBeat Blog

Perfect Monitoring for Your Cloud

API access for our uptime monitor

Today we published AppBeat 1.3.6 with following features:

  • "Account / API Access" - possible to call first AppBeat REST method which returns status overview of your system. This allows you to create your own simple client. We will add more useful methods in future.
  • security improvement: same application session can not be used from multiple IP addresses
  • we are now displaying question dialog when new web client is available (you can also postpone version upgrade) --> this will be visible first time when next version arrives
  • back-end upgraded to .NET Core 1.0 RTM
  • other minor improvements

API access is currently simple (just one method), but now we have solid infrastructure on which we can build. Next we will try to add REST method for measuring page speed from different locations. Website speed will be measured on remote browser and will also download all page resources (CSS, scripts, images, ...).

.NET Core 1.0 was officially released yesterday at Red Hat DevNation. Few hours later we already had our entire web backend migrated to RTM version. Because all internal tests were positive, we decided to push it to our production environment - less than 24 hours since official announcement :) This is what we call agile development :)

If your current version does not update to 1.3.6, simply press CTRL+F5 in your web browser. This should reload your page and replace cached version with new one.

Dynamic webhooks for integration with any notification provider (and more)

Today we published AppBeat 1.3.5 with following features:

  • added context menus for services, checks and contacts for more clean user interface
  • when you right click on check in "Service & Checks / Checks", there is new "Failure/success notes..." option. This allows you to include additional instructions for your support staff for each check and is included in sent notifications.
  • "Account / Personalization" - possible to customize notification subject and short message (SMS) template
  • "Account / Integrations" - added dynamic webhook provider which supports request customization - can be used with any notification provider that supports JSON payload
  • check name is now included by default in notification subject and short message
  • "Account / Security" - current password must be entered before changing to new password
  • other minor improvements

Context menu support:

When user clicks on check with right button, context menu is shown

Failure/success check notes:

Notification templates:

Dynamic JSON webhooks: