How we upgraded our monitoring front-end to .NET 5

How we upgraded our monitoring front-end to .NET 5
Today we upgraded our Linux based web frontend from .NET Core 3.1 to .NET 5 and here are step by step instructions what we did. First we uninstalled old .NET Core versions because they are not needed anymore. We identified .NET related packages with following commands: sudo apt –installed list | grep “dotnet” sudo apt –installed list | grep “asp” Then we uninstalled old packages with: sudo apt-get remove –purge PACKAGE_NAME We ensured Microsoft repositiories are setup:
Read more →

AppBeat monitoring is now powered by .NET Core 3.1

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!
Read more →

AppBeat was upgraded to .NET Core 3.0

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.
Read more →

.NET library for detecting temporary / disposable email addresses

Hello. We published open-source, simple and easy to use .NET Standard 2.0 library with some useful utilities. For example, you can now easily check if email address is temporary / disposable. With string extension methods this can be as easy as following: bool isTemporary = “[email protected]”.IsTemporaryEmail(); //true Current implementation is offline (known temporary domains are “baked in”) and for this reason also very fast. GitHub repository with examples: https://github.com/AppBeat/AppBeat.Utils Our official NuGet Package for this library: https://www.
Read more →

Coming soon: recurring unmonitored time functionality

Soon you will be able to define recurring time periods when service and all its child checks will be temporary excluded from monitoring: This may be useful for some customers who don’t need 24/7 monitoring and don’t want to use our API integration to pause / resume service with web services. New feature will be added as part of our 1.8.0 application version upgrade in it is scheduled to be publicly available in beginning of 2018.
Read more →