An RPM (RedHat Package Manager) package is the file format used by RHEL and CentOS, and their package manager yum (now called dnf). Since NetEye is based on CentOS, we use this standard package manager for distribution. How an RPM is constructed is defined in so-called spec files. In this blog post I’m going to…
Read MoreIn the last few weeks, we collaborated with the Icinga2 developers to create a new powerful API, called “Execute Command“. The main purpose of this new API is to execute specific commands on a node by sending the request to the parent node. This is useful when the user cannot reach the desired node (an…
Read MoreAs already mentioned in my previous Blog Post, I would like to present our Design System project, based completely on Vue.js. It’s not just a modern UI component library. The whole purpose of a Design System is to define the design principles, style guide, patterns, content tone, and the rules and specifications of “reusable” components….
Read MoreNetEye is a constantly evolving solution that allows you to monitor the status of heterogeneous objects and collect metrics from different sources. Properly correlated, this data can become an important source of information for your business. With the 4.13 release we added an important tool that allows you to manage data: we upgraded InfluxDB to…
Read MoreIn this article we’re going to take a look at the main tool for validating PHP code and explain in detail how to check the code we write so we can contribute it to Icinga Web 2 and its modules. First, let’s talk a little about coding conventions and what’s the standard for PHP projects….
Read MoreThe official Icinga 2 user guide is quite extensive, but it’s not always complete. That’s normal in today’s world of fast changing software where the focus is on delivering new capabilities quickly. Even here at NetEye most of the documentation we produce for our user guide is written when we add new modules and features,…
Read MoreA piece of code can’t be considered good if it doesn’t work properly. One of the questions that arises from the previous sentence is, “So how can I know that my code is actually doing what it’s supposed to be doing?” The quick and easy answer is: Tests. But how can you decide which types…
Read MoreEvery software suite needs documentation. But the more features we add to NetEye to meet customer needs, the larger the user guide becomes. Over time, it’s important to make sure that the guide continues to meet the needs of NetEye users despite this. In particular, modern methodologies like Agile that we use in NetEye often…
Read MoreIn my last user guide blog I showed you how to create your own menu item, create a space on the file system, write a sample page, and store an image for that page, all in a way that will survive future updates. This time I want to show you how to use your custom…
Read MoreIn my last post, I showed you how to set up your own customized documentation in NetEye 3 so that it won’t be overwritten when you upgrade. Doing the same thing in NetEye 4 is also possible even though there isn’t a dedicated link for external documentation like in NetEye 3’s DokuWiki, and there isn’t…
Read MoreWouldn’t it be great to have quick access to your favorite pages in the NetEye documentation? To make customized thumbnail pages of your most frequent screenshots? To create your own alternative documentation index with categories reflecting your mindset? To add your own notes, comments, or FAQ with pointers into the existing NetEye documentation? That would…
Read More