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.

Hello Everyone! As Feu had mentioned in their post earlier this week, we are restructuring how we work and how we communicate. From maintaining the project, to developing, to doing our events and working with you – the community. We see that we have been underperforming in a few aspects of our work: mainly the open communication with our open source community, and we want to change that.

In February we released the first version of our new Icinga for Windows monitoring. Within a short amount of time we received a lot of feedback from different test and customer environments. Thanks to your testing, feedback and reports we were able to track down additional issues on the framework itself. Today we are happy to announce Icinga for Windows v1.0.1 – fixing issues especially with service user handling and one issue with the Icinga Director Self-Service API.

We have talked about it for a long time, but now it is here: The Icinga DB RC1 In case you managed to avoid all of the talk about it, Icinga DB is the replacement for our IDO (Icinga Data Output). What does this mean for you? It means SPEED. Especially for larger environments. So, what’s in the RC? It is basically a finished product. We want to give both you and us some time to test it out, find bugs and get comfortable with it.

We’re happy to announce a new version of icingabeat, v7.5.2. With this release we ensure the compatibility with Elasticsearch 7.x and Logstash 7.x. Icingabeat is an Elastic Beat that fetches data from the Icinga 2 API and sends it either directly to Elasticsearch or Logstash. To get you data forwarded, icingabeat connects to the Icinga 2 event stream and receives all events happening within Icinga in real time.