AppBeat Blog

Perfect Monitoring for Your Cloud

Domain expiry monitoring with Whois

With newest version of AppBeat you can now periodically run Whois for your domain:

You can customize notification rules to receive message when domain is about to expire or set custom regular expression for Whois response:

For example, you can set regular expression to ensure correct name servers, registrant name, domain status, or any other information returned from Whois server.

Please let us know if you have any questions about this feature. Happy monitoring!

Best Pingdom / UptimeRobot alternative?

Do you own website or blog and want to be informed when it becomes inaccessible? Maybe there is an issue with your web application or web server becomes unresponsive and you want to resolve issues as quickly as possible?

AppBeat is right tool for you and now, for limited time, we offer you 75% discount on Standard yearly plan which includes 15 one-minute checks.

To get this discount just use promo code MONITOR during checkout and your price should be automatically discounted from 49.90 EUR / year to 12.47 EUR / year.

This is just 1.04 EUR / month for 15 one-minute checks or 0.07 EUR / check / month and includes:

  • one-minute check frequency
  • unlimited email alerts & third-party integrations
  • 10 free SMS messages per month
  • log history saved for 12 months
  • multi-user login
  • free public status page
  • and much more (please check our pricing for details)

Have questions? Please contact us and we will be happy to help.

Hurry up and grab this deal while you can!

Time for change? Affordable Pingdom alternative.

Our website monitoring solution is now available for two years and we have upgraded it with cool new features:

  • unlimited email alerts and integrations with HipChat, OpsGenie, PagerDuty, Pushover, Slack, StatusPage, Workplace by Facebook or dynamic webhooks
  • monitoring of HTTP(S), HTTP/2, IPv4, IPv6, Ping, SSL, DNS, UDP, TCP, IMAP, POP3, SMTP protocols
  • free public status page with easy option to use it on your own domain, for example
  • access to our monitoring API for integration with your system
  • log history saved for 12 months
  • support for multi-user login
  • industry-standard encryption to protect the confidentiality of your sensitive information
  • 100% service level agreement (SLA) available
  • ...and much more!

Engineered for rock-solid reliability

Since launch in 2016, our core monitoring service has effective uptime of 100%. This is of course not a coincidence since one of our main design goals was eliminating single point of failure by:

  • using geographically distributed failover clusters,
  • using high availability and geo-replicated database,
  • having fault tolerant microservice architecture for our monitoring agents.

Want to try it? No problem, we offer you 14-day free trial (no obligations, no credit card required). Have questions? Please let us know.

Happy monitoring!

p.s. if you migrate your monitors from Pingdom, UptimeRobot, StatusCake or any other uptime monitoring service, you are eligible for 50% discount on any yearly AppBeat plan. Interested? Please try our free 14-day trial and contact us.

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.

Stay tuned :)

Receive huge website monitoring discounts!

Website monitoring discounts are now available:

  • receive 50% discount when switching from another monitoring provider
  • receive up to 90% discount for recommending AppBeat on social media or web page
  • recommend AppBeat to another user / company and receive free credit upon their purchase

Please contact us for more details!

Note: discounts can not be combined

How to create public status page for your domain or service?

Want to share your latest monitoring status with your users? Want to notify your visitors about scheduled maintenace /downtime? You can do this very easily with AppBeat:

  • login to your AppBeat account (or create one for free)
  • click on "Public status" and then "Enable public status page"
  • configure if you want your status to be automatically updated by AppBeat (and for which monitored services)
  • your public status can then be hosted on:
    • your web server / your domain by copy/pasting our high-availability JavaScript snippet on your page
    • our web servers / our domain (
    • for Advanced plans and higher: we can host your public status on our AWS infrastructure (yearly plans can also have free certificate for secure HTTPS version of public status page) - please contact us so we can send you instructions for DNS entry on your domain


Have questions? Please let us know.

How to get notification before SSL certificate expires?

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, ...).

Simple as that!

Migration of our monitoring stack to .NET Core 2.0 and .NET Standard 2.0

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 .NET Framework on Windows (.NET Framework 4.6.1 and newer)
  • security and performance improvements


We started official migration from .NET Core 1.0 as soon as Microsoft released RTM version of .NET Core 2.0 and Visual Studio tooling. Entire process went quite smoothly and without major issues. We followed official instructions published on Microsoft Docs (very useful).

During migration, most time was spent for resolving NuGet conflicts and we also encountered one runtime problem with Entity Framework Core 2.0 - we resolved this by doing simple workaround and rewriting this one problematic query. Everything else was - perfect!


Our migrated solution is now deployed on Windows and Linux production servers and everything runs without any issues. Improvements on web front-end are very noticeable (Kestrel, compiled MVC views, smaller deployments). Mission accomplished!

Thanks to Microsoft and all open source contributors for making such a great product!

Want less monitoring alarms? Introducing quiet hours!

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:

When you click "Add quiet hours for" button for specific resource, you will be presented with dialog similar to this:

You can add multiple quiet hours for same resource, AppBeat engine will always aggregate those entries while determining if quiet hour is effective or not.

Here are some use case examples:

  • you have service which is not operational 24/7 - now you can simply set quiet hours when service is not active so you don't receive any alerts
  • you have recurring (nightly) updates and you want to mute alerts during this period
  • you don't want to receive alerts for less important service(s) during weekend
  • your team member goes on vacation or sick leave and you don't want to bother him/her with outage alerts
  • some of your team members receive alerts only during working hours (and you have dedicated team for 24/7 operations)
  • etc.

Happy monitoring!