Today we are happy to announce, that Icinga for Windows v1.7.0 has been released! While this release includes lots of bugfixes for the Framework itself including the basic plugins, our main goal was to increase usability and make access for developers a lot easier.
00:10 Why are there some issues and PRs that have not been looked at for some time?
01:34 Are there plans to increase the number of people working on the Director?
01:51 Why is there such a discrepancy between the HA functionality in Icinga 2 versus Icinga Web 2 and its modules? And will this improve in the future?
03:17 Will it be possible to tunnel module traffic with the Icinga traffic? Is something planned for managing for example x509 in a distributed setup?
We all know that the history data is important in monitoring. But this history data becomes obsolete over time and those records become garbage which would only fill up space. So it is important to remove obsolete history records to free up space. We call this process housekeeping. This needs to be performed periodically to cleanup the history records whenever they exceed their maximum age and become obsolete.
The Docker images we provide for both Icinga 2 and Icinga Web 2 already contain quite a number of modules. For example, the Icinga Web 2 image contains all the Web modules developed by us. But one of the main benefits of Icinga is extensibility, so you might want to use more than what is already included. This might be some third-party module or a custom in-house module.
When redesigning the new Icinga DB Web interface elements we already started establishing consistent design elements. This is even more supported by developing the Icinga PHP Library (IPL) from the ground up. IPL makes developing reusable widgets a lot easier for developers. For the release of Icinga DB Web RC2 we’re going the extra mile to polish many of our user interface elements.
Today I show you a snapshot of my daily work. It is especially interesting this time, because it’s a not-so simple problem to solve. It’s not difficult per se, but involves quite some understanding of the Icinga Web 2 framework and how it communicates with the web server. Disclaimer: What I’m going to show, is not a feature preview or anything. It’s more of a proof of concept, and it may be that forever and won’t be continued further.
You’ve probably been in this situation before – you’re using Icinga to monitor your infrastructure and Icinga detects a critical issue but nobody notices it. It might be an urgent maintenance request, an unexpected breakdown, or a service quality issue. But your technicians or service engineers are neither in the control room nor in front of the dashboard to see the issue and its urgency.
