Have more than 50 periodic web monitors and want to save some money? You are not satisfied with your current monitoring service quality? Don’t worry, we have something special for you! In December 2016 and January 2017 we offer you three months free service for any of our paid packages! In this free period you will experience our superior service quality, without monitoring outages or false positive detections! Our solution was architected from the ground up with reliability and robustness in mind.

That is our goal for next year! We want to offer you real browsers, for example Chrome and Firefox, so you can periodically check if your web application always behaves as it should. This kind of service will be very useful for your continuous integration and testing your website after you deploy new version into production environment. If you would like to participate in closed beta, please contact us.

We like C#, .NET and .NET Core! Last time we played a little bit with traceroute utility and thought, could we write something fast, efficient, and since we love Asynchronous Programming with async and await (C#), something that would include this pattern as well? Here is what we came up with :) using System; using System.Diagnostics; using System.Diagnostics.Contracts; using System.IO; using System.Net.NetworkInformation; using System.Text; using System.Threading.Tasks; namespace AppBeat.Core.Utility { public class TraceRoute { private const string DATA = “AppBeat Monitoring - https://appbeat.

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!

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: