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.
After weeks of rewriting the core aspect of Icinga for Windows – executing checks – we are happy to announce version 1.5.0 today. Why we changed the check handling? We are glad you asked and happy to share the new features!
If your team is using Atlassians Jira and Icinga and you didn’t know about our integration yet: Our module for Jira is now at version 1.1.0 with a bunch of bugfixes and new features that were requested on the GitHub repository. Our friends from the internezzo ag helped out by sponsoring the development as well – a big THANK YOU to them!
The question is (probably) older than monitoring itself: Who monitors the monitor? While Icinga comes with countless options to monitor a wide range of devices and applications, at some point you will ask yourself how you can observe if Icinga itself is having errors.
Icinga is the perfect, powerful monitoring stack that helps you tackle your monitoring challenge. It´s open source and free to use for anybody – be it a private person, a non-profit organization or a commercial company.
In this blogpost I will introduce, how to create a business process from monitored hosts and services and how to add them to dashboards. Business Process module is an interesting module in Icinga Web 2. It allows you to visualise and monitor hierarchical business processes based on any or all objects monitored by Icinga. We can create custom business process and trigger notifications at process or sub-process level.
These days many setups have a lot of redundancy and you may not want to send notifications during the night, just because one of multiple http servers has a problem. This blog post will show you how to setup a single service with a state combining multiple other services.
Have you ever been in a situation where something in your Icinga configuration did not work as expected and you ended up doing small changes and reloading Icinga over and over again? This can be especially tricky with apply rules and filters if they don’t match the objects you hope for. This post will show you how you can use the Icinga Script Debugger in this situation to get an interactive console in the context where the apply rule or filter is evaluated.
User Interface design or product design in general is less about tools than it is to have a proper understanding about the product you work on. And besides understanding, how the user is going to use your product, recognizing patterns and underlying relationships between key elements is crucial. Besides that, there are some tools, that really enable me to iterate quickly on ideas and concepts and then communicate these to the team.
One of the focuses of version 2.9 of Icinga Web 2 will be on access control. For years on now, Icinga Web 2 had a very simple role based access control (RBAC) implementation. This suited most of our users fine. However, there were still some requests to enhance this further. The next major update of Icinga Web 2 (Version 2.9) and Icinga DB Web will allow users to configure exactly this.
