Login to your AppBeat account (or create new one if you don’t have it yet). Click “Add new periodic monitor” and select “SSL Certificate” as shown on screenshot below: Click “Next” button and enter your URL: Click “Next” and close wizard with “Finish”. Your certificate will now be periodically monitored and when it is about to expire (30 days or less - you can change this in check settings), you will automatically receive notification (we support email, SMS, Slack, web hooks, …).

After successful migration of our monitoring front-end, back-end and microservices to .NET Core 2.0 and .NET Standard 2.0, here is quick summary of this process. Migration decision Although we were very very satisfied with .NET Core 1.0, we decided for migration to newest version for following reasons: bigger API and more libraries available (thanks to .NET Standard 2.0) much easier to share common internal projects between .NET Core 2.0 and Full .

In newest AppBeat version 1.7.0 you can now define quiet hours for your users, services and/or third-party integrations (I will refer to these as “resources”). Quiet hours are recurring time periods during which alerts (outgoing notifications) are muted for selected resource(s). Quiet hours does not affect monitoring, just notifications. This means that you will always be able to check log entries, even during effective quiet hours. You can access this new feature from “Alerting” module and by clicking “Quiet hours” tab as shown below:

We are currently implementing experimental subset of WebDriverIO API (higher level API on top of Selenium WebDriver) in .NET Core so we could run synthetic (transaction) monitoring very efficiently from different geographic locations. Implementation goals: cross-platform, efficient and lightweight framework easy to use (REST API / web interface) high compatiblity with WebDriverIO because users are already familiar with it for security reasons we will probably implement simple JavaScript interpreter for WebDriverIO commands (instead of running tests in Node.

We slightly updated our notification rules for new website checks. Reason for this update is only “cosmetic” - new rules will generate better descriptions for outgoing notifications and log files. New rule for status “Error” [trigger_rule: 5xx server error rule] %STATUS% >= 500 [trigger_rule: 4xx client error rule] %STATUS% >= 400 New rule for status “Warning” [trigger_rule: warning by 3xx redirection rule] %STATUS% >= 300 AND %STATUS% < 400 New rule for status “Good” %STATUS% >= 200 AND %STATUS% < 300