Bug Fixes for NetEye 4.37
We fixed a bug in nginx that was causing NetEye upgrades from version 4.36 to version 4.37 to fail with an error. We updated the following packages:
Read More
Blog Entries
Perform KNN Classification Using Elasticsearch
Hey everyone! We played around a bit last time with our radar data to build a model that we could train outside Elasticsearch, loading it through Eland and then applying it using an ingest pipeline. But since our data is in the form of vectors, could we actually exploit Elasticsearch vector database functionality and perform…
Read MoreBug Fixes for NetEye 4.37
Core Neteye install, update, upgrade procedures individual service logs weren’t saved in the correct format We resolved a small issue where logs from parallel install or configurator playbooks were wrongly manipulated resulting in a different format from what they were supposed to be saved. SIEM – Log Management Elastic Stack missing systemd configuration files We…
Read MoreNetEye 4.38 Release Notes
Release date: 1st October 2024 Welcome to version 4.38 of our NetEye v4 Unified Monitoring Platform. The Church of St. John in Ranui, set against the breathtaking Dolomites in the Funes Valley, welcomes you to this release. This historic gem, nestled in the heart of South Tyrol, is a testament to the region’s rich cultural…
Read MorePrevent Elasticsearch Crashes Using Disk Watermarks
Hi all, it’s been a while. I’m deeply sorry not to have sent out some blog posts lately, so now I’ll try to get back your trust by providing some useful information. Not only that, I’ll even go out of my comfort zone: instead of NetEye Core and monitoring strategies, I’ll talk about NetEye SIEM…
Read MoreMonitor your Elasticsearch Shards Count
Elasticsearch limits the number of open shards per node with the max_shards_per_node cluster setting, which defaults to 1000. The limit on the total number of shards is then calculated from this setting with this formula: total_max_number_of_shards = cluster.max_shards_per_node * number of non-frozen data nodes If the total number of shards is reached either by a…
Read MoreBug Fixes for NetEye 4.37
We fixed a procmail misconfiguration that was occurring after the upgrade. We updated the following packages:
Read MoreBug Fixes for NetEye 4.37
We resolved an issue in the neteye update and neteye upgrade commands where the process would halt if the Elasticsearch cluster took longer than 30 seconds to respond to API requests. We updated the following packages:
Read MoreBug Fixes for NetEye 4.37
We resolved a bug in the nginx configuration for our clickhouse integration. This fix guarantees that queries will no longer be directed to the voting-only node in cluster environments, preventing potential errors. We updated the following packages:
Read MoreBug Fixes for NetEye 4.37
We fixed a bug in the neteye update procedure. In particular, this now handles properly the update of pacemaker and corosync, as done already by the neteye upgrade. This enhancement guarantees proper pcs resource management throughout this phase. We updated the following packages:
Read MoreBug Fixes for NetEye 4.36
We fixed a bug in the neteye update procedure. In particular, this now handles properly the update of pacemaker and corosync, as done already by the neteye upgrade, to ensure a correct handling of the resources during this phase. We updated the following packages:
Read MoreHow to Integrate Metrics Collected in OpenShift into NetEye/Grafana
OpenShift already has a built-in monitoring suite with Prometheus, Grafana, and Alertmanager. This is all well and good, but what if organizations want to monitor their entire infrastructure, integrating all monitoring results under one umbrella? In this case, it’s necessary to send the metrics somehow from OpenShift to NetEye. In this tutorial, I’ll show you…
Read MoreBring Your Own Model – Using Custom Models in Elasticsearch
Hey everyone! As you may remember, we took a look in the past at how it’s possible to use a model (trained directly in Elasticsearch) to perform some real time classification by using an ingest pipeline. But… what if we wanted to use our own externally trained model? Well the good news is that, under…
Read MoreBug Fixes for NetEye 4.37
A bug in the NetEye Alyvix integration has been resolved. This bug was associated with certain secure attributes that were absent from the cookie responsible for storing the Alyvix JWT token. We updated the following packages:
Read MoreBug Fixes for NetEye 4.37
We fixed a bug that under certain conditions caused notifications of a state change to be lost during the execution of a deployment and at the same time Tornado would perform an action to set a check result. We updated the following packages:
Read More