A domain in “Registrar Lock” status means the registrar for that domain has locked the domain to prevent any unauthorized domain transfers / changes. Our domain monitor can check domain expirations but did you now you can also check domain locks? In AppBeat “Check” wizard, go to last step “Health status rules” and modify your Warning rule into something like this: [trigger_rule: domain expires soon] %EXPIRES_IN_DAYS% <= 30 [trigger_rule: domain not locked!

We migrated our BlogEngine blog to Hugo and deployed it to Amazon S3. Our blog is now effectively serverless because we don’t have to worry about servers and upgrading our blog engine with latest security patches :) Bonus: excellent performance results with overall score A - 100 Wow, just wow!

Here are short instructions how to integrate your AppBeat Monitoring with PagerDuty. Login to your PagerDuty account and create or select existing service Click on “Integrations” tab and click “New Integration” button: Enter your integration name, select “Use our API directly” with option “Events API v2” and click “Add Integration” button: 4. Now you should see your new integration with generated “Integration Key” (you will later use this key in AppBeat).

On December 3rd, .NET Core 3.1 RTM was officially released and we decided to upgrade our monitoring solution to newest version since this is Long Term Support (LTS) release. Because AppBeat was already running on .NET Core 3.0, upgrade was really easy and without any issues. After few days of testing we are now running newest version in production :) Happy monitoring!

Our monitoring service is now upgraded to newest stable release of .NET Core 3.0. Entire process took us about 30 minutes :) This was done in preparation for migration to .NET Core 3.1 which should be released in December 2019. Newest version brings performance, security and functionality improvements.