iLert is an alerting and on-call management solution for ops teams and helps you to respond to incidents faster. It extends monitoring tools such as Icinga with advanced alerting through SMS, phone calls, and push notifications and lets you easily manage on-call duty with schedules and escalations. iLert is a SaaS company based in Germany and has been an integration partner with Icinga for over 5 years. This blog post outlines some of the features by using Icinga along with iLert.

Today we are proud to announce the next major release of Icinga for Windows: Version 1.1.0. Besides new core features that we added to the Framework itself, we also provide additional components to extend the features of our solution. Thanks to the increased usage in our community we collected lots of feedback that we considered and implemented for better usability and flexibility.

Icinga Web 2 and all its modules have been localized from the very beginning. There were also quite a few languages added. Just recently Icinga Web 2 and the Director got a Japanese locale! And a updated Russian as well as a new Spanish (Argentina) locale are in the works at the moment. Over the years our Saudi Arabian, German, Finnish, Italian, Japanese, Brazilian, Russian and Ukrainian users were able to experience Icinga Web 2 and some of its modules in their native tongue.

The Business Process module is used to visualise all the objects in Icinga in a hierarchical format. This way, you can visualise your data in a way that fits its application! You can create custom process-based dashboards and trigger notifications at process or sub-process level. You can also have a quick top-level view for thousands of components on a single screen.

Today we will be talking to Noah Hilverling, or “N-o-X” on Github. He’s been with the Icinga team for almost 4 years now and is responsible for a whole lot of bug fixes and shiny features in Icinga 2.

When we started the development of Icinga 2 we had a clear picture. We wanted a great monitoring solution for small and large environments. Back then, we imagined Icinga 2 to be a scalable monitoring tool with a dynamic configuration, enriched with a slight and fast web interface. In fact, there were some more details to that. But let’s keep it short. We worked hard to achieve our goals.

When building Icinga DB Web we completely rewrote the basic Icinga Web UI. The “monitoring module”, which it was called before. While this existed for some time and the and the underlying concepts were already used in the Icinga Director, we took the chance and brought our Web UI to a new level. In Icinga IPL every UI element is represented by a PHP class.

During the past few months while working on Icinga DB, we have tested our existing libraries on how we work with data and how we present them programmatically. Maybe it was because we were doing something new with Icinga DB or we weren’t entirely happy with the existing code. In any case, it was time for new libraries :-). The IPL – Icinga PHP Library was born. And we want to share that work starting with ipl/Sql an OOP SQL abstraction for PHP.

While creating a Docker image, one of the most important decisions to make is what base image to use. In this post I’ll compare three kinds of base images for you.

Last week we finally had our first virtual Icinga Meetup. Since we had some trouble at our very first try, we were even more excited and nervous about this. This time, after a couple of minutes it was clear that everything will go well from the technical perspective. We were prepared content-wise as well and almost all of the registered attendees showed up. Experiencing the first couple of minutes going so well was a huge relief and, in the end, the whole meeting was a great event.