We are super excited to announce a major milestone in our company history. 10 years ago, iLert started with a simple mission: help companies to increase their uptime and deliver a seamless digital experience. Every feature in iLert is built to help you to respond to critical alerts faster and increase your uptime.

This post highlights some of the features and improvements that we have released in the last 6 months.

Our ecosystem continues to grow: we have added 10 new integrations within the last months. Integrations are the bridge between alert sources and on-call teams and have always been a top priority at iLert. They are one of the reasons why iLert is so easy to adopt for small and large companies alike.

This post covers some of the highlights that we have released in the last 6 months.

Many companies are continuously modernizing their infrastructure – but there is no standard way for the perfect IT infrastructure. Still, hybrid architectures have become the status quo in enterprises. Almost all organizations have migrated at least parts of their assets to the cloud or run applications as cloud services. At the same time, businesses want to dovetail their IT architecture with software development and are therefore embracing dynamic infrastructures. ‍

Cologne, Germany – iLert GmbH, a SaaS company for alerting, on-call management, and uptime monitoring, announced today that it has achieved the Amazon RDS Ready designation, part of the Amazon Web Services, Inc. (AWS) Service Ready Program. This designation recognizes that iLert has demonstrated successful integration with Amazon Relational Database Service (Amazon RDS).

Kubernetes is hard, but lets make monitoring and alerting for Kubernetes simple! At iLert we are creating architectures composed of microservices and serverless functions that scale massively and seamlessly to guarantee our customers uninterrupted access to our services. As many others in the industry we are relying on Kubernetes when it comes to the orchestration of our services.

We’re proud to introduce our latest addition to iLert’s advanced reporting capabilities. On-call reports give on-call engineers and managers insights into all-things on-call and report three metrics: The data can be filtered by data range and schedules. If a user is on two or more schedules at the same time, that time is counted once. This information can be used in various ways.

At iLert we embrace infrastructure as code and try to automate our processes whereever possible. This might reach from niftly little bash scripts to fully blown Terraform projects that spin up whole environments with as little as terraform apply on a CLI. With Hashicorp’s Terraform you can make use of infrastructure as code to provision and manage any cloud, infrastructure, or service.

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.