Operations | Monitoring | ITSM | DevOps | Cloud

This is a guest blogpost by Markus Opolka from the Icinga Enterprise Partner NETWAYS. After forking the Grafana Module for Icinga Web last year, we started thinking about alternative ways to display Icinga performance data graphically in the web interface. Running a separate Grafana instance just to render graphs is a lot of overhead and adds operational complexity — no matter how much you like Grafana. Plus, installing the grafana-image-renderer isn’t always straightforward.

After NETWAYS has already taken a leading role in the past in maintaining the Ansible Collection Icinga, contributing features and bug fixes, it’s now official: The Ansible Collection Icinga is moving into the NETWAYS namespace (on GitHub and Ansible Galaxy). The people involved in the repository will remain largely the same.

We’re excited to share that Icinga for Kubernetes v0.3.0 is here! This release is packed with features designed to make monitoring your Kubernetes environments smoother, smarter, and more efficient. Let’s take a closer look at what’s new.

In the dynamic world of IT operations, a common misconception has emerged: Observability vs Monitoring is often framed as a battle where one replaces the other. At Icinga, where open-source monitoring is our expertise, we aim to clarify this misunderstanding. Observability doesn’t supplant monitoring—it complements and enhances it. The term “Observability” has become a buzzword in the tech industry, often touted as the modern solution to outdated, static monitoring practices.

In recent months, the IT monitoring landscape has seen notable investment activity: These developments are part of a larger trend, with investment firms showing growing interest in the IT monitoring sector. Although such activity isn’t unusual in the tech industry, the current intensity and frequency indicate that IT monitoring is emerging as a key area for growth-oriented strategies.

Designing user interfaces for Icinga Web is always a bit of a balancing act. Once we’ve worked through all the technical and conceptual details of a new feature, it can be tough to step back and see things from a fresh user’s point of view. We as developers know too much — and that makes it hard to guess how others will understand what we’ve built.