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 MoreElasticsearch 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 MoreWe fixed a procmail misconfiguration that was occurring after the upgrade. We updated the following packages:
Read MoreWe 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 MoreWe 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 MoreWe 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 MoreWe 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 MoreOpenShift 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 MoreHey 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 MoreA 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 MoreWe 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 MoreWe 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 MoreWe 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 MoreWe fixed a bug that caused the tenant drop down, in the NetEye Alyvix integration, to not display the full list of tenants in case of users who are not administrator of NetEye but have Full Module Access on the Alyvix module. We updated the following packages:
Read MoreWe fixed a bug that caused the tenant drop down, in the NetEye Alyvix integration, to not display the full list of tenants in case of users who are not administrator of NetEye but have Full Module Access on the Alyvix module. We updated the following packages:
Read More