Some time ago, we started research and development efforts to create components for Icinga aimed at monitoring Kubernetes environments. Over the past months, we have gained valuable insights into the platform and how we can monitor Kubernetes with Icinga efficiently.

Have you ever admired those cool graphics on the web? They look nice but can be the wolf in sheep’s clothing. In this post you will learn about SVG injections and how to avoid them.

Have you ever experienced configuration issues, such as notifications not being sent as expected or apply rules not matching all expected objects, probably due to an incorrectly set custom variable? Icinga 2 has several options to assist you in such situations. Last time, Julian demonstrated how to analyse such problems using the icinga2 object list command. Today I will show you how to interactively investigate your problem using the mighty Icinga 2 debug console.

We take pride in our diverse range of customers and users worldwide who trust Icinga for their monitoring needs. That’s why we’re 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.

In the dynamic realm of monitoring Kubernetes clusters, effective visualization is paramount for gaining insights into system health and performance. One versatile tool that has gained prominence in this domain is Scalable Vector Graphics (SVGs). In this blog post, we’ll delve into the usage of SVGs, explore different implementation methods, weigh the pros and cons, and discuss why they are indispensable for monitoring Kubernetes with Icinga2.

Today, I want to showcase an old, but still very useful, tool when it comes to analyzing and debugging an Icinga 2 configuration: the icinga2 object list command. It can be helpful in a variety of situations, for example when you want to verify that a config change has the desired effect, but also for finding out where something is set in the configuration.

For users using monitoring module, migrating their custom dashboards, navigation items and permissions and restrictions to Icinga DB Web has been made easier with the recent Icinga DB Web release (v1.1.1) through its migrate command. Once Icinga DB Web has been upgraded to v1.1.1, run the command icingacli icingadb migrate --help to see the avaliable actions under migrate command and what each action does.

Monitoring your systems is like having a superhero keeping an eye on your digital realm. And when it comes to superheroes in the world of monitoring, Icinga takes center stage. But did you know that Icinga becomes even mightier with the help of components? In this post, we’re going to unveil the top three Icinga components that are not just cool but downright essential for your monitoring game.