We are happy to announce the release of Icinga Web Jira Integration v1.3.0 today. You can find all issues related to this release on our Roadmap.

Today we’re announcing the general availability of the Icinga Cube in version 1.3.0. You can find all issues related to this release on our Roadmap.

Tenacta Group is an Italian company with a portfolio of worldwide leading brands that share the same mission: to develop designs and technological innovations that will improve people’s quality of life. We have been using Icinga since its early days, specifically version 1 after the fork from Nagios. We have continued using Icinga because we like its direction for future improvements and appreciate the support of the Icinga community.

To speed up startup and reload times of Icinga 2, we have already put a lot of effort into improving the configuration load performance and still continue to do so for the next major release. In this blog post, I will share the story of one particular issue we found, how we addressed it and what impact this has.

It’s the year 2009, a nice weekend in late spring and a small group of monitoring enthusiasts comes together to discuss how to move forward with the idea of forking Nagios. The Icinga team in 2009, just to set the mood. Plans were made to make it faster, easier, more scalable, and simply better. Of course, such a project has a lot of hurdles to take – the most important one was of course: the name.