November 21, 2016

Better website monitoring experience for your team

We deployed our upgraded rule engine. You can now have more descriptive notifications for Warning and Error rules, by combining them together with custom note: [trigger_rule: my notification message: why so slow???] %RESPONSE_TIME% > 10000 [trigger_rule: server X needs restart???] %STATUS% = 503 AND MATCH(%RESPONSE%, “YOUR_REGULAR_EXPRESSION”) If conditions for trigger are met, you will automatically receive notification with your note. This may be useful in critical situtations for your team, so they can respond more quickly!

November 19, 2016

Coming soon: multi expression rules for better monitoring experience

Very soon we will add multi expression support for Warning and Error notification rules. Syntax will be as following: [trigger_rule: YOUR_RULE_NAME_1] EXPRESSION(S)_1 [trigger_rule: YOUR_RULE_NAME_2] EXPRESSION(S)_2 [trigger_rule: YOUR_RULE_NAME_N] EXPRESSION(S)_N On user interface this will look something like this: This example rule then triggers “Warning” notification which is sent to you and it is also visible in monitor log:

November 16, 2016

Should we support more rich rule expressions?

We are seriously considering to upgrade our rule engine with option to specify multiple Warning or Error rules by using “named expressions”. In current version you can write quite complex expressions, but they trigger generic Warning / Error message. Our idea is to allow users to specify multiple named Warning / Error expressions which would give you more information / context. For example, in Warning rule you could have something like this (expression with two rules):

November 11, 2016

Source code for our website monitoring command line tool

As we have previously promised, we published full source code of our cross-platform website monitoring command line tool. You can get it from https://appbeat.io/automation/cli/source-code Tool is written in C# and targets cross-platform .NET Core framework. This means you can run it on Windows, Linux or Mac. Tool currently supports following commands: AppBeat Command Line Interface for monitoring automation, version 1.0.0 Usage: dotnet AppBeat.CLI.dll [command] [options] command: help Displays this help.

November 8, 2016

Houston, we have a mobile app!

The AppBeat Android app lets you connect to your AppBeat uptime monitoring service from anywhere, anytime. You can view current live status of your checks and do basic check management: • create simple web checks • pause/resume specific check or entire group of checks For more powerful management you can always login to our web application at https://appbeat.io where you can: • view uptime / downtime reports, performance reports and incident reports

October 31, 2016

Android beta testers needed!

Would you like to participate in beta testing of our companion Android app for website monitoring? Drop us an email on https://appbeat.io/contact p.s. testers will also receive discount codes for our paid plans

October 22, 2016

Sneak peek: AppBeat website monitor client for Android

Early development version of AppBeat monitoring client for Android: One of our main goals is simplicity! What do you think?

October 13, 2016

How to integrate AppBeat website monitor with PagerDuty?

Please follow this simple integration guide: https://www.pagerduty.com/docs/guides/appbeat-integration-guide/

October 8, 2016

Our website monitor now supports Pushover and StatusPage

Yesterday we published AppBeat 1.4.6 which now natively supports Pushover and StatusPage. With Pushover you can now easily receive outage notifications on your Android or iOS phones, and with StatusPage you can automatically publish detected outages on your public status page. With this version we also add support for message personalization for most third-party integrations: All third-party integrations can be managed in “Account / Integrations” section:

September 27, 2016

How to periodically run SSH commands and trigger AppBeat alert

In AppBeat 1.4.5 we introduced support for running SSH commands where you can trigger monitoring alert by checking result of: command exit status code (for example you can simply trigger error if exit status code is not 0) checking specific text in standard output (stdout) by running regex expression checking specific text in standard error (stderr) by running regex expression You can add new SSH monitor by clicking “Add new periodic monitor”, enter monitor name and from “Agent type” select “Run Secure Shell (SSH) command”: