Nowadays, a working digital infrastructure is the lifeblood of almost any organization. The impact of a major IT incident can go far beyond the IT department, affecting a company’s revenue or incur costs in other areas of the business caused by service disruption. Therefore, in addition to the technical response to a major incident from the IT department, business stakeholders need to be involved as well, so they can prepare the business response.

Imagine you are rolling out your application to multiple customers, they even might use it on premise. Of course you want to know if your application is running fine and the customer is not experiencing any kind of trouble or downtime - surely you would not want to ship this validation in your own system, as that might also be prone to any kind of error at some point. Which is why you decide to go for a third party uptime monitoring solution e.g. Uptime Monitoring.

We are really excited to announce that Christian Fröhlingsdorf joins iLert as our Chief Technology Officer. Christian brings significant experience from senior roles in large industrial companies. He has held various positions within the REWE Group and played a key role in developing and growing a large microservice-based e-commerce marketplace for online grocery retail.

At iLert we are big friends of dogfooding as we love to take our features and check out any way possible to hack or integrate them. We have launched the auto-raise feature for support hours in early 2020 and they really are a fancy way to setup wake-up calls in the morning.

We’re extending iLert’s reporting capabilities with detailed incidents reports.

After a closed beta test of 3 months, we’re finally making Uptime Monitoring in iLert generally available. And the best of all, uptime monitoring will be included on all our existing plans at no additional cost.

With Priority-Based Alerting, you can set different notification rules for high and low priority incidents.

Keep it quiet during maintenance. With maintenance windows, you can temporarily disable one or multiple alert sources for a set period of time. An alert source with an ongoing maintenance will not create any incidents.