In December 2022 we decided to completely restructure the code of our User Guide. Previously, each project contained its own documentation, but this led to very difficult and time-consuming development having the code scattered across more than 40 repositories. Furthermore our contributors are not necessarily NetEye developers, or even developers at all. Setting up a…
Read MoreThe Beginning When I started my new role as a DevOps Engineer at the beginning of 2022, we had little experience in DevOps as a team. We tried several times to implement automation in order to simplify maintenance and reduce the amount of overall effort we invested in routine activities. However, since DevOps engineers are…
Read MoreLooking at how several companies have managed their services, we discovered a relatively new (for us) technical role, the Site Reliability Engineer. As IBM reports: The principle behind the SRE is that using software code to automate oversight of large software systems is a more scalable and sustainable strategy than manual intervention – especially as those…
Read MoreIn our migration journey from multiple VMs to OpenShift, one mandatory step is the integration with our company’s Active Directory. This is the default IdP for our services like Jenkins, NetEye, etc., and we want to centralize authentication and permissions as much as possible. Integration with OpenShift is less straightforward than it is with other…
Read MoreIn a previous blog post I described how we installed our first OpenShift cluster and how we used HA Proxy as a load balancer. Our cluster is meant to host both internal services (like CI and docker registry) and public services, and we thus have to expose them on multiple domains with valid SSL certificates….
Read MoreWithin our Research and Development team we maintain a set of both physical and virtual machines for many purposes: internal repository mirrors, CI/CD, testing, internal docker registry, etc… Maintaining them is demanding, especially considering that our infrastructure has grown over the years and was often configured by different colleagues using different software and tools. And…
Read MoreDuring our implementation of the NetEye migration to Red Hat 8 we decided to drop our internal mirror for system packages and instead rely on Red Hat’s official repositories. Our goal was to improve reliability, speed up the delivery of updates, and alleviate the development team’s workload. But it also introduced a new issue: we…
Read MoreWe fixed a wrong behaviour which causes neteye satellite config create to do not work when executed with –tenant parameter. For NetEye 4.22 we updated the following packages: elasticsearch, elasticsearch-autosetup, elasticsearch-neteye-config, filebeat, filebeat-autosetup, filebeat-neteye-config, apm-server, apm-server-autosetup, apm-server-neteye-config, kibana, kibana-autosetup, kibana-neteye-config, logstash, logstash-autosetup, logstash-neteye-config to version 7.15.0_neteye3.37.2-1
Read MoreThe current Elasticsearch license bundled with NetEye will expire this January 31st. To continue enjoy all the SIEM functionalities you must update to the new license. An automatic update has been released for the most recent NetEye version. Older NetEye releases however, can be updated manually. In the case the health-check light/01004_elastic_license_check.sh is preventing you…
Read MoreWe fixed three bugs in NetEye 4.21: a bug that prevented the user to import Saved Object using Kibana GUI a bug that prevented the user to enrich the logs going through El Proxy with Elasticsearch Ingest Pipelines a bug in documentation which makes unclear in certain situation whether to execute command on the standby…
Read MoreDuring 2021 we decided to officially support Satellites as part of NetEye. Satellites were already widely used by our customers, in particular as part of the Icinga 2 monitoring infrastructure, but a complex manual configuration was required to install them. The development team faced a difficult challenge in fully supporting Satellites: providing an easy-to-use solution…
Read MoreWe fixed a bug in NetEye 4.21 which prevents the correct creation of resource telegraf_tornado_monitoring in cluster environment with stopped resources. For NetEye 4.21 we updated the following packages: neteye-setup to version 1.82.1-1
Read MoreWe fixed a bug in NetEye 4.20 which causes ILM with deletion phase to be applied to ELProxy Acknowledge indices. A second bug that was fixed was related to the event adjustments in the SLM, which in certain cases where not retrieved and correctly from the database and then displayed accordingly on the SLM report….
Read MoreWe fixed a performance bug in NetEye 4.20 which caused long downtimes while creating or upgrading batches of NetEye Satellites. Now Icinga2 will restart only once at the end of the full configuration procedure, speeding up the Satellite configuration and reducing downtimes. For NetEye 4.20 we updated the following packages: icinga2, icinga2-autosetup, icinga2-bin, icinga2-common, icinga2-debuginfo,…
Read MoreWe fixed a bug which prevents the activation of log signature via Icinga Director for hosts with hostname different than FQDN. Another bug we fixed was causing neteye_secure_install to fail in the cluster environment when influxdb was restarted. In addition, we fixed the background of the quick navigation that was transparent in some conditions. For…
Read More