One of my clients with a number of routers installed at their own remote location asked me if I could analyze the network flows at multiple locations. Their network architecture is a full mesh, and thus has private subnetworks, data center environments, and even in some cases cloud providers. Complex architectures like this require increasing…
Read MoreNetEye installation topology can fluctuate over time, with hosts of various types that can be, for example, added or removed from a cluster in response to changes in business demand or customer requirements. In a cluster environment, hosts are manually mapped in a file called /etc/neteye-cluster, a sort of static inventory solution that is the…
Read MoreWelcome to version 4.20 of our NetEye v4 Unified Monitoring Solution. NetEye welcomes the autumn and its new release with a majestic sunset panorama view on Seceda peak in Dolomites Alps. The Alpe di Seceda is located on the sunny side of Val Gardena, at the foot of the Parco Naturale Cisles-Odle (nature reserve). From…
Read MoreHow can we allow a Tornado administrator to successfully track down the flow of an event through Filters, Rules and Actions of Tornado, when Tornado is processing thousands of events per second? Tornado administrators can have a hard time reading Tornado logs to understand where for example an action error comes from. Take this log…
Read MoreWe fixed a bug which prevents nats-server to automatically start after reboot on NetEye Satellites. For NetEye 4.19 we updated the following packages: nats-server and nats-server-autosetup to version2.5.0_neteye1.12.3-1
Read MoreWe fixed multiple bugfixes related to telegraf and nats-server: A security issue related to the nats-user telegraf, now the user has been replaced with two different users telegraf_ro and telegraf_wo in order to improve security An issue that restricts telegraf consumers to write metrics from the master subject to INFLUX A new telegraf consumer which…
Read MoreWhenever a new monitoring project gets underway, a consultant discusses with the customer about almost any related topic: what needs to be monitored, how to monitor it, when to implement it, how to represent performance data, etc. Based on customer needs and desires, any sort of implementation strategy can be planned, but almost all of…
Read MoreIntroduction The Cisco APIC is the main architectural component of Cisco ACI. It’s the unified point of automation and management for the Cisco ACI fabric, policy enforcement, and health monitoring, and it optimizes performance and agility. In this article we’ll integrate this solution into the NetEye platform using a simple and customizable approach Solution The…
Read MoreIn my second and last blog I want to talk about the procedure for writing Icinga Web 2 modules (icingaweb2-modules) for NetEye. This will be my last blog because as of today, I will sadly leave this company. In my short time here I’ve had the occasion to learn the art of making own Icinga…
Read MoreWe fixed a bug that caused the yum groups “neteye” and “neteye-tools” to not being marked as installed on some NetEye instances. For NetEye 4.19 we updated the following packages: neteye-setup to version 1.75.1-1
Read MoreWe fixed a bug that caused the ES_CLUSTER_INITIAL_MASTER variable to be overwritten when a new Elastic-only node was added to the cluster. For NetEye 4.19 we updated the following packages: apm-server, apm-server-autosetup, apm-server-neteye-config, elasticsearch, elasticsearch-autosetup, elasticsearch-neteye-config, elasticsearch-xpack-license, filebeat, filebeat-autosetup, filebeat-neteye-config, kibana, kibana-autosetup, kibana-neteye-config, logstash, logstash-autosetup, logstash-neteye-config, logstash-neteye-config-autosetup to version 7.12.1_neteye3.30.3-1
Read MoreWe fixed a bug in the Analytics Module that sometimes failed to render a custom dashboard correctly. We fixed also a bug in the ntopng SSO that didn’t allow the users with the “.” (dot) contained in the username to log in correctly. For NetEye 4.19 we updated the following packages: icingaweb2-module-analytics, icingaweb2-module-analytics-autosetup to version…
Read MoreWe fixed two bugs in Logstash: an issue related to corrupted jvm.options configuration files, which prevents Logstash from starting properly a pipeline bug will cause Logstash to index every time in the same index which will grow up infinitely if a proper rollover template is not defined For NetEye 4.19 we updated the following packages:…
Read MoreWe fix a userguide bug about the procedure to migrate the Nats Server to a supported configuration. For NetEye 4.19 we updated the following packages: nats-server and nats-server-autosetup to version 2.1.7_neteye1.12.1-1
Read MoreWe updated Icingaweb2 to the latest bugfix. For icingaweb2 module tornado we fixed a wrong validation of the rule WHERE clause, we fixed some errors that appeared with viewer users, and finally we fixed the event type label in the test event window. For NetEye 4.19 we updated the following packages: icingacli, icingaweb2, icingaweb2-autosetup, icingaweb2-common,…
Read More