Jira Module for Icinga Web 2 As many of you are aware, at the end of 2019 Icinga released the first version of a Jira module for Icinga Web 2. This module gives Icinga Web 2 the ability to query Atlassian Jira Service Desk for issues related to Hosts or Services and, of course, to…
Read MoreAt the beginning of the year, the OCS and GLPI asset management solutions were integrated into NetEye 4. And so we have been increasingly implementing projects in this environment. In fact recently I was once again able to activate and configure a ticketing system in GLPI for a customer. It’s always amazing how easy it…
Read MoreLive Meeting – 15th of July, 11.00 AM In this highly requested session we will explain how we have enhanced NetEye and the integrated ntopng offering to take into account network monitoring challenges due to the global lockdown. Traffic has increased over 45%, and in some cases even over 50%, and weekend evening peak traffic saw…
Read MoreIncreasingly often, monitoring tools are the recipients of the notifications that are sent when problems arise, in order to guarantee the resolution of those problems quickly. In some circumstances, we need to extend the default type of communication that has historically been used: email. In this blog post I will describe how we integrated NetEye…
Read MoreWe fixed a bug, that would not allow adding a custom role to the pre-configured user for Elasticsearch in Logstash. To solve this bug, we have implemented the PKI authentication (certificate authentication) for the Elastic Logstash user. The roles assigned to the Logstash user are provided via role mapping. We already updated the Logstash Elasticsearch…
Read MoreFixed icinga2-master systemd logs filling up journalctl For NetEye 4.12 we updated icinga2 icinga2-autosetup icinga2-bin icinga2-common icinga2-debuginfo icinga2-doc icinga2-ido-mysql icinga2-ido-pgsql icinga2-neteye-config icinga2-resources icinga2-selinux to version 2.11.3_neteye1.17.1-1
Read MoreBeats is the new method for log acquisition introduced in the latest releases of NetEye 4. It’s a system fully integrated with the Elastic Stack. The Beats agents send logs directly to Logstash, which then forwards them to Elastic. Logstash also writes each log received into files on the file system (at the same location…
Read MoreBeginning in NetEye 4.12 we introduced the neteye upgrade command, which enables NetEye users to automatically and safely perform a number of tasks needed to complete a NetEye upgrade, both in single instance environments as well as in cluster environments (have a look here for more information about the neteye upgrade command). In order to…
Read MoreBecause of its open source nature, NetEye 4 combines loads of different technologies, which makes it impossible to identify “the” NetEye 4 Tech Stack. Based on RHEL/CentOS 7, most of the user-facing parts are written in, or at least proxied through, PHP, whereas there is no real common denominator for other backend services. This looks…
Read MoreUpgrading a NetEye 4 installation, either as a cluster or a single instance, is not always a painless activity. NetEye 4 is, in fact, a very sophisticated product that offers its customers a very large number of features, and operates in complex and business-critical environments. From version to version, the upgrade procedure may change: as…
Read MoreHave you ever wanted to open a ticket in Jira Service Desk when NetEye 4 highlights a problem? Here’s a recipe for connecting NetEye 4 to Jira Service Desk Cloud.
Preparation Time: About 20 minutes
Difficulty: Easy
Ingredients …
The Tornado module is improving release after release. With NetEye 4.12 we reached one of our main goals: Tornado is now configurable within the graphical interface, and you can now create new nodes and rules, or edit and delete your existing ones. The icingaweb2-module-tornado module (i.e., the graphical interface of the well-known Tornado module) is…
Read MoreAs a NetEye User I want to handle node failures when they happen in my cluster. When a node becomes unresponsive, it might still be accessing your data: the only way to ensure that a node is truly offline is to shut it down. This procedure is called fencing. NetEye 4 relies on Corosync/Pacemaker, also…
Read MoreFixed some old Search Guard reference in the User Guide. For NetEye 4.12 we updated: icingacli icingaweb2-selinux icingaweb2-vendor-Parsedown icingaweb2 icingaweb2-vendor-dompdf icingaweb2-vendor-zf1 icingaweb2-autosetup icingaweb2-vendor-HTMLPurifier php-Icinga icingaweb2-common icingaweb2-vendor-JShrink icingaweb2-devel icingaweb2-vendor-lessphp to version 2.7.3_neteye1.72.3-1
Read MoreNetEye 4, thanks to the Director module, offers very powerful mechanisms when it comes to fetching data from external data sources. Among the external resources that can be configured in NetEye 4 there is clearly LDAP / Active Directory. This type of resource can be used for multiple purposes: Authentication of users Import of LDAP…
Read More