You might have noticed that we’ve added a new type of alert source a few months ago - Heartbeat alert sources: A Heartbeat alert source expects a signal (the “heartbeat” ping) at regular intervals and alerts you, if it doesn’t receive a ping within the specified interval.

This post outlines how to use Zabbix and iLert with multiple on-call teams, where each team is responsible for a set of host groups in Zabbix, and therefore, will only receive alerts for the services it is responsible for. But first, let’s start with the basic needs when being on-call.

When working with IoT (internet of things) devices one of the key issues is to keep track of the health of all installations. Most of the time, especially with smaller devices, the applications (firmwares) are flashed for a single time during setup and stay untouched at their location of action for a long while.

How many servers can be managed by one system administrator? This question is pretty hard to answer since it depends decisively on the tasks that need to be operated. It is clear, however, that the amount of servers one engineer can manage has increased tremendously over the time, and is still growing. Public and private clouds, in combination with automation tools, enables us to automate many daily tasks. In a modern IT infrastructure almost everything can, and should, be automated.

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.