Operations | Monitoring | ITSM | DevOps | Cloud

June 2021

Monitor Windows without an Icinga Agent

Looking to monitor your Windows systems with Icinga, but aren’t allowed to install non-Microsoft certified software on them? Then you are in the right place. After all, you want to monitor your systems somehow. But you don’t want to lose the support from MS afterwards, just because you installed a monitoring system on it. Well, today I will show you how to monitor your Windows without having to install the Icinga agent.

Contributing to Open Source

If you’re here you probably know the essence of open source already. To us, open source means more than just open source code – it’s also the ethics and the community feeling that goes along with that. For us it means that the people working on Icinga are more than just who we see in our office – Icinga lives from your ideas and contributions. And we want to invite you to join in on the fun!

Introducing dark and light theme modes

We are constantly working to make Icinga even better by adding new useful features. We will be releasing Icinga Web 2 version 2.9.0 very soon. This version will have many new interesting features. One of these functions gives you the option to change the theme mode to Dark, Light or Auto. The default Icinga theme will come with all three modes and will use Dark as the default theme mode. You can change it at any time in the account preferences.

Icinga for Windows: Hyper-V and Cluster Plugin Release v1.0

After months of developing and testing, we are finally ready to announce the release of our Icinga for Windows Hyper-V and Cluster plugins version v1.0 today! We collected lots of feedback, tested different approaches and re-designed some plugins to ensure we can provide good monitoring basics for these environments, allowing us to improve and extend them in the future.

Bring your own CI/CD.

As a developer I couldn’t imagine working without one of these three things. For projects on GitHub the built-in actions should do the latter job fine in most cases. But as everything else they have limits. The more PRs, the more different tests per pull request and the longer those tests run, the longer different PRs have to wait for each other for the continuous integration to run.