A safer way to run privileged Windows checks with SystemRunner If you’ve been monitoring Windows for a while, you’ve probably seen this pattern: some checks must run as LocalSystem (S-1-5-18), and the “quick fix” is to run the Icinga Agent itself as SYSTEM. It works. It’s also a really bad idea. Why? SystemRunner takes a…
Read MoreRecently Icinga DB Web had a new security release, fixing a vulnerability where protected or hidden custom variables could be inferred by any user with object visibility by abusing comparative filters on those hidden variables.
Read MoreAmong the several plugins that Grafana provides is Node Graph, a useful plugin for visualizing elements and relationships between them. This plugin, as described in the article: https://grafana.com/docs/grafana/latest/panels-visualizations/visualizations/node-graph/ , can be used to represent: To verify its usefulness within NetEye, we adapt it to the data present in Icinga. In this POC, we import our…
Read MoreImportant: Icinga2 security update Type/Severity NetEye Product Security has rated this update as having a High security impact. Topic An update for the icinga2 packages is now available for NetEye 4. Security Fix for NetEye 4.44 CVEs The CVEs include three different vulnerabilities: an Information Disclosure, a Denial of Service and a Limited Privilege Escalation. For a detailed…
Read MoreDuring one of my last sessions with a customer I had to deal with a very particular use case, where I couldn’t use the solution presented in my previous blog post (https://www.neteye-blog.com/2025/08/massive-update-of-the-icinga-custom_var-host-services/). In this new scenario, the customer wanted to clean up a custom_var linked to a service, whose value, inherited from the host, had…
Read MoreOne feature that’s widely used by customers for the enrichment of entities (hosts/services) within Icinga is custom_var. These can be used for a variety of reasons: to provide more information to end users about a device, faster classification, to integrate data used by other tools such as notification, etc… These variables can be managed directly…
Read MoreWhat’s What NetEye is a comprehensive IT Monitoring and Observability platform developed by Würth Phoenix. It’s based on open-source tools like Icinga, NagVis, Grafana, Elastic Stack, among others, and is tailored for enterprise IT infrastructure monitoring, IT Operations Analytics (ITOA), and IT Service Management (ITSM). NagVis is an open-source visualization tool that provides graphical representations…
Read MoreIcinga 2 is a powerful monitoring system that helps you keep track of your infrastructure. But like any monitoring tool, it can generate a lot of logs. Over time, these logs can accumulate, making it increasingly harder to find the critical information you need. If you’re using Icinga 2 on a Windows system, you might…
Read MoreOur older customers surely know that, in its earliest releases, NetEye 4 had no support for multitenancy. From a data perspective, there’s just one big bin we throw everything into to be used later. Then, a debate about multitenancy began. Here at Würth Phoenix we’ve discussed at length about the best way to segregate data…
Read MoreAfter updating to NetEye version 4.38 and activating authentication via Keycloak, the Icinga Director Self Service API no longer works. For instance if you install the Icinga agents using a Powershell script that automatically creates the host objects in the Icinga Director when it’s called, then this process will no longer work. That means you…
Read MoreIcinga Director is a powerful configuration tool included in NetEye that streamlines the process of defining and managing monitoring configurations. However, you may encounter issues with duplicate addresses and spaces in hostnames, which can lead to confusion and monitoring inaccuracies. In this post, I’ll discuss these common problems and introduce a Grafana dashboard solution to…
Read MoreToday I want to present an Icinga 2-based monitoring use case where concepts of the powerful Icinga 2 DSL functional language come into play. The use case is based on mapping the status of a Host/Service Object via passive check results only. For this kind of use case, any accidental active status check could potentially…
Read MoreI don’t really know the reason behind it, maybe because the typical scenario for notifications is just “send all events to this mailing list”, or as we say: set it and forget it. But we shouldn’t use this as an excuse: monitoring projects now consist of tens of thousands of objects (hosts plus services), and…
Read MoreCurrently, deploying an Icinga 2 Agent on a Linux system can be intricate, given the substantial variations in the process across different releases or OS families. For instance: Fortunately, there’s no need to develop and maintain a custom script to manage these diverse scenarios. We can leverage the readily available Ansible Plugins for this purpose….
Read MoreScenario NetEye 4 is a comprehensive monitoring platform which natively supports Icinga 2 checks on remote hosts and devices. Several Icinga 2 checks support an historical view of the status. An example is the firewall interface performance status below, which displays a Performance Graph: Getting a better overview All the graph data generated by the…
Read More