After the government recently passed a law asking everyone to limit travel and gatherings, I decided to only shop online. I’m not alone in this – many other people decided to do this too, bringing the sites that provide these services down to their knees, since a large number of users were all trying to…
Read MoreWith the rapidly advancing digitalization of the economy, the availability of IT is becoming business-critical. Unplanned downtime is no longer acceptable, 24/7 operation is indispensable. For administrators, this means that they have to identify incidents before they lead to damaging behaviors in business processes. AIOps promises support in this direction. The digital transformation or our…
Read MoreWe fixed the exclusion, from the Logstash file input filter, of the logs created by Beats, which caused Logstash to go OutOfMemory For the GeoMap module we fixed a bug that generated an error when clicking on the Map Detail tab. For NetEye 4.11 we updated: elasticsearch, elasticsearch-autosetup, elasticsearch-neteye-config, elasticsearch-xpack, elasticsearch-xpack-autosetup, kibana, kibana-autosetup, kibana-neteye-config, kibana-xpack,…
Read MoreAs you may already know from our other blog posts, Würth Phoenix is an official partner of the German company SOS Berlin, the creator of the SOS JobScheduler. In our role as partner, we not only resell the JobScheduler solution, but also offer consulting activities for SOS JobScheduler implementations, sizing and so on. Today I…
Read MoreFor the SLM module, we fixed the error message shown in the report form when an invalid contract is selected. For NetEye 4.11 we updated: icingaweb2-module-slm, icingaweb2-module-slm-autosetup to version 3.5.4-1 icingaweb2-module-neteye to version 1.58.2-1
Read MoreFor the SLM module, we fixed an exception that was thrown when an availability contract for an SLM customer with no user attached to its role exists in the NetEye and a user with another role tried to access the availability contract page. For NetEye 4.11 we updated: icingaweb2-module-slm, icingaweb2-module-slm-autosetup to version 3.5.3-1
Read MoreUntil the NetEye 4.10 release, the Tornado module inside NetEye handled communications between its components (the Tornado Collectors and the Tornado Engine) via direct, clear-text TCP connections. On local systems, this configuration does not represent a limitation, since in this case there is no requirement to verify the identity of the peer (it is always…
Read MoreWe fixed a bug that hid the Grafana dashboard Performance Graph link inside the Host monitoring view if the user had full module access to analytics and monitoring. We added constraint to protect from deleting the SLM contracts in use. We also fixed a bug that happened when a user had the monitoring restriction to…
Read MoreRelease Date: March 31, 2020 Welcome to version 4.11 of our NetEye v4 Unified Monitoring Solution. The complete changelog, which includes all fixed issues, can be generated on demand by following the instructions in the updated NetEye documentation. To begin the upgrade, please follow the instructions in your current NetEye version at User Guide > Upgrading…
Read MoreFixed a bug that affected the signature of logs written by Logstash when receiving data from Beats. For NetEye 4.10 we updated: elasticsearch, elasticsearch-autosetup, elasticsearch-neteye-config, elasticsearch-xpack, elasticsearch-xpack-autosetup, kibana, kibana-autosetup, kibana-neteye-config, kibana-xpack, kibana-xpack-autosetup, logstash, logstash-neteye-config, logstash-neteye-config-autosetup, logstash-xpack, logstash-xpack-autosetup to version 7.4.0_neteye2.7.4-1
Read MoreInfluxDB is the database used in NetEye for saving performance data. It guarantees graphic visibility of the data (thanks to the Grafana frontend) and it is very important that the data stored is useful. I’ll give you an example of how simple it can be to produce obsolete data in Influx: Suppose I create a…
Read MoreWhen designing complex systems with a multitude of services, more often than not some of them logically form loosely coupled units. Usually these services should remain independent to a degree, i.e. free to be started or stopped independently. However, we also wanted a mechanism to command the loosely coupled unit as a whole. Sometimes however…
Read MoreSince my latest blog post on the new Front End automated tests, we have improved our Continuous Integration process. In this blog post, I describe, from the developer’s perspective, a couple of important enhancements and what we would like to achieve in the upcoming months. The introduction of pull requests has been the first change:…
Read MoreIn a previous post, Valentina showed us how to configure Slack Notifications… and here I will similarly show you how to configure Telegram notifications on NetEye. Create a Telegram Bot A very easy way to create a bot on Telegram is through … another bot 😉 BotFather is a Telegram bot dedicated to the creation…
Read MoreIn this blog post I will describe a potential use of Tornado to monitor events in near real-time, while keeping historical information about the received events. Use Case Often as a user I want to collect data from different sources, e.g. Windows events, and then according to some simple rules set the status of some…
Read More