Icinga for Windows is our framework and plugin collection to monitor Windows hosts natively with the Icinga Agent. We published our first release candidate in November, today we are delighted to announce the availability of Release Candidate 2 of Icinga for Windows. Thanks to your feedback and tests during the past weeks, we were able to improve the entire solution and increase the stability and reliability.
Our journey of Icinga integrations continues – we’re announcing the general availability of the Icinga Module for Jira v1.0 today! Jira is a ticketing system created by Atlassian and it’s one of the most popular ones of its kind. Jira is used by a very diverse audience: Developers, Managers, SREs, Systems Engineers and everyone else who needs to keep track of issues and projects.
During the past years we made plenty of contributions to improve the current state of the Windows monitoring. We tried to improve the actual installation with the Icinga 2 Powershell Module, allowing users to easier automate installation and configuration of Icinga 2. On a long term we however wanted to improve the monitoring of Windows infrastructures entirely, by not only providing new plugins but also to increase the contribution by the community.
Following Icinga’s development and gathering valuable insights can be time consuming. So we thought about trying something new: Icinga Insights, a live stream on Youtube packed with interesting details on a given topic. As you may have heard, Icinga 2.11 was the biggest release ever done. We’ve invited Michael to join the conversation with Christian this time. Originally targeting 1 hour time, we had a lot of fun during the stream and just kept talking.
Over the last four years, the Icinga Director has grown from an optional configuration add-on to a mature Software product with lot‘s of features. Most Icinga installations are now driven by the Director, no matter whether they are small or huge, manually curated or fully automated.
Now we are here, after many months of development – we proudly release Icinga 2.11 available today. It has been an emotional ride with many changes under the hood. The most obvious change is that Icinga’s distributed cluster operates more stable, the past quirks with hanging certificate signing requests or dead-locked TLS handshakes are now gone.
Some say you have to move all of your server infrastructure into the cloud. Others counter that you should keep your data safe and secure in your own datacenter. And then there are many people in between who use cloud services as an addition to their self-hosted servers. In fact, there’s no right or wrong, because as always in IT: It depends. We at Icinga always try to find a way to make everyone happy with their monitoring – be it in the cloud or on premise.
We are proud to announce that icinga.com is now also hosting integrations of hardware for monitoring environmental sensors and alerting via text message. The devices from the manufacturers listed on Icinga Integrations can easily be implemented into your Icinga monitoring by using plugins provided on Icinga Exchange.
When we hunt down problems in Icinga setups we ask for logs most of the time. While you get used to sifting through logs and collect some bash magic during the process there’s always the wish for this routine to be easier and especially faster. If you get logfiles from several days where each of the nodes produces millions of logfiles per day, every time you start your grep’s over and over get’s you madder and madder. So I started searching for a solution.
