Some years ago, one of my colleagues wrote an article about how to “Avoid Tornado Rules Repetition with a Map Post-modifier”. He presented an interesting and very useful way for creating Tornado rules without rewriting them. The core of his approach was based on the Mapping modifier, a functionality in the previous Tornado GUI that…
Read MoreCustom Variables are widely used in the NetEye 4 (Icinga) monitoring system in order to tag/add information to a host/service. In order to speed up setting these variables, users use the inheritance mechanism to inherit them from parent objects (i.e. hosts). This feature is very useful, but sometimes it can create some doubt about what…
Read MoreMonitoring systems acquire information from various devices in different ways: API, SNMP, syslog, etc. One of the most important methods in Icinga-based systems like NetEye is the Icinga Agent. This agent is installed on each server and collects and sends information to the master NetEye node using secure protocols. When we work within a small…
Read MoreTornado is a CEP “Complex Event Processor” that receives reports of events from data sources such as monitoring and email, matches them against preconfigured rules, and executes the actions associated with those rules. Some vendors provide static notification systems that cannot be customized. For example, during one project we were faced with a tool that…
Read MoreCommvault software is an enterprise-level data platform used to back up, restore, archive, replicate, and search data. The software is available across cloud and on-premises environments, and a lot of customers are using this solution as part of their infrastructure. And in such situations the necessity arises to develop a solution for integrating COMMVAULT information…
Read MoreIntroduction In this article I’ll introduce a feature that some customers have frequently asked for. The customers’ request is linked to the fact that automation (whether via Tornado, ad-hoc scripts, etc.) generate a lot of services “on the fly”, for example as shown in my previous blog post. These services are created, updated and eventually…
Read MoreIntroduction As introduced in a previous post, Cisco’s APIC is a core component for several of our customers; it’s a complex solution that every user can employ to fully customize their configuration. There I explained how to monitor the APIC at a high level, summarizing the fault information tenant by tenant. Some customers needed to…
Read MoreUPSs are critical devices that need particular attention when you’re monitoring them. Most of them are not very performant with respect to SMNP requests you send them. For this reason, passive monitoring via SNMP traps is the best solution. In this way, monitoring doesn’t burden the hardware with useless requests. In this session we’ll look…
Read MoreThanks to automation, migration between NetEye 3 and NetEye 4 can be easily performed for a lot of entities such as hosts and services. But additional elements like parent-child relationships can be missed. So we implemented a procedure for mass-migration of this information from the old platform to the new one. Solution In the NetEye…
Read MoreIntroduction The Cisco APIC is the main architectural component of Cisco ACI. It’s the unified point of automation and management for the Cisco ACI fabric, policy enforcement, and health monitoring, and it optimizes performance and agility. In this article we’ll integrate this solution into the NetEye platform using a simple and customizable approach Solution The…
Read MoreIntroduction The nTop application is one of NetEye’s integrated solutions for network traffic monitoring. In order to test its scalability, we decided to build a test bench where we could simulate a customer who needs to monitor a large number of devices (i.e., 1-2K routers) and wants to group this information at the nTop level…
Read More