With the release of Icinga Web 2.12, we’ve streamlined and simplified the process for performing database schema upgrades for both Icinga Web and its modules. This new feature not only indicates when an upgrade is pending but also allows for automatic execution of the upgrade. Previously, users had to consult the upgrade documentation and perform the upgrade manually. While it’s still important to read the upgrade documentation, this new feature simplifies the process significantly.

This release has the version 0.1.0 and is available via our package repositories. Be sure to check the documentation on how to install it. So what is Icinga Notifications actually? It is not possible to explain every single detail now. We will eventually publish separate articles on our blog, which will go into more detail about topics this post only mentions briefly.

I’ve already dropped a hint at this topic in a previous post of mine which reflected the history of Icinga on Windows: And this time I’m going to prove this concept, since both required components have been released by now: Icinga 2.14 and IfW 1.11. Precisely speaking, an existing Icinga master will run checks remotely on Windows, directly via the IfW REST API – without an intermediate agent.

As a software developer in training at Icinga, I’ve learned a lot about the nuances and importance of monitoring systems. Effective monitoring is critical for maintaining the health, performance and security of any infrastructure or application. Here are ten essential tips to help you develop an effective monitoring strategy.

Finally, we are pleased to announce the availability of the new Redis* open source server packages for Icinga DB for all supported distributions . You may have already noticed that we had some issues with the previous packages here and there, but we’ve been working on them for months and now they’re finally available for you to use.

One of the major strengths of Icinga is its capability to integrate with many other tools to automate and scale IT infrastructure monitoring. Today, we’re happy to announce the certification of an integration between Icinga and NetBox. The solution was developed over the past four years by our enterprise partner Sol1 and will be jointly supported by all Icinga, Sol1, and NetBox Labs, the commercial steward of NetBox.

There is always a big debate about whether interpreted or compiled languages are more useful. I think it is important to look at the pros and cons. Both language types have their strengths and weaknesses. While interpreted languages are great for maintaining and modifying software, compiled languages usually outperform them in terms of performance and packaging.

When writing a custom check plugin for Icinga 2, there are situations where in addition to observing the current state of a system, taking the past into account as well can be helpful. A common case for this is when the data source provides counter values, i.e. values that increase over time and you are less interested in the current value but more in how it changes.

We take pride in our diverse range of customers and users worldwide who trust Icinga for their monitoring needs. That’s why we’re showcasing some of these enterprises with their Success stories. It’s stories from companies or organizations just like yours, of any size and different kinds of industries.

We are excited to release two new versions today: Icinga DB v1.2.0 and Icinga DB Web v1.1.2.