With Icinga DB Web you can now customise Icinga Web’s list views to your needs. While in one scenario you might be more interested to see as many objects as possible at a glance, in another scenario detail attributes of only a few objects will be more important to you. Yet, in the first case, you would even be distracted by more detailed information.
When interacting with the Icinga 2 API, the client is commonly authenticated using a password provided via HTTP basic auth. Icinga 2 also support a second authentication mechanism: TLS client certificates. This is a feature of TLS that also allows the client to send a certificate, just like the server does, allowing the server to authenticate the client as well.
We´re proud of our many customers and users around the globe that trust Icinga for critical IT infrastructure monitoring. That´s why we´re now showcasing some of these enterprises with their Success stories. It´s stories from companies or organizations just like yours, of any size and different kinds of industries. Some of them are our long-standing customers, others have just recently profited from migrating from another solution to Icinga.
We’ve been working on a bunch of minor releases lately. Today we’re happy to announce new versions for Icinga 2, Icinga Web and the Icinga DB Web module. Check out the details below.
In the scenario where you want to execute tasks repeatedly at a specific time and have full control over when they are executed and how the results are handled, it makes sense to build this into your application instead of setting up a cron job, for example. I’d like to give you a quick example of how you can achieve this in PHP using two great libraries, ReactPHP and cron-expression. ReactPHP is an event-driven programming library that has an event loop at its core.
A few years ago, we introduced a new, completely independent library. The IPL – Icinga PHP Library, a bundle of Icinga PHP libraries. Since then we are actively working on further development and adding new features. Today I would like to highlight individual parts of this library and the tasks they perform.
Like I’ve mentioned in my last blog post, we use GitLab pipelines for packaging. We have a lot of software, like Icinga, Icingaweb and its various modules, which we want to build across multiple different operating systems. This results in a huge number of jobs and pipelines, doing very similar stuff. We have a lot of code repetition, and this is bad – code repetition means higher code maintenance , and it invites bugs.
One of Icinga’s greatest strengths is its ability to integrate with other systems and use those systems’ data to enrich monitoring. It can write time-series data to InfluxDB, Graphite or even Prometheus with our icinga2-exporter. It can talk to different data sources so that hosts and services can be created and managed automatically. This means that lots of manual work is eliminated.
Nobody likes resolving merge/rebase/cherry-pick conflicts. I also don’t, but I’ve found a scheme how to reduce the built-in headache. In this post I’m going to share my findings as well as practical examples.
We’re excited to announce our next major release for Icinga Director, version 1.10! The new release comes with plenty of fixes, but also with some nice new features. Check out the full changelog for all details.
