We have resolved an issue that could have led to the failure of the installation process during initial setups. This problem arose from a temporary absence of an entry in the /etc/hosts file, which in turn hindered the startup of nginx. We updated the following packages:
Read MoreWe have implemented a verification step in the neteye install, update, and upgrade processes to verify Kibana’s connectivity to the fleet integration endpoint when the NetEye instance operates behind a proxy without direct Internet access. Additionally, we have revised our User Guide to provide detailed instructions on configuring this aspect. Moreover, the rolling restart process…
Read MoreWe updated the Elastic Stack to version 8.15.2, which fixes some known issues present with versions 8.15.1 (the version previously used in NetEye for Elasticsearch, Kibana, Logstash and APM) and 8.15.0 (the version previously used in NetEye by Elastic Agents and Beats). For more details please refer to the official Elastic release notes. We updated…
Read MoreWe 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 MoreHey 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 MoreCore 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 MoreRelease 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 MoreHi 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 More