These days we live in a data-driven world, where the collection and analysis of data empowers not only companies but also individuals to plan future actions based on the information that is extracted. NetEye enables both the collection and analysis of an enormous amount of data using various platforms, such as Kibana, for data written…
Read MoreWe fixed a bug for which the healthcheck 00400_local_neteye_target_services_are_disabled was failing on NetEye Satellites due to some services enabled by default on the NetEye Satellites. The healthcheck now does not control the state of such services on Satellites. For NetEye 4.22 we updated the following packages: neteye-setup to version 1.83.4-1
Read MoreWe fixed a bug for which the healthcheck 01220_telegraf_retention_policy_set was failing on NetEye Satellites. The healthcheck is now skipped on Satellites. For NetEye 4.22 we updated the following packages: icingaweb2-module-analytics, icingaweb2-module-analytics-autosetup to version 1.48.3-1
Read MoreToday my objective is to collect the performance metrics from various NetEye Icinga checks and write them out to Elasticsearch so I can apply Machine Learning (ML) algorithms to identify potential anomalies. This is a task that’s not possible with the open-source version of InfluxDB installed in NetEye. Moreover, this data in Elastic is used…
Read MoreRecently a customer told me he would like to monitor and graph the values that his Fortigate Firewall was generating for his configured SLA Trackers. What are these SLA Trackers? I informed myself and found the following in a Fortigate Cookbook. Fortigate Performance SLA ─ Link Monitoring Performance SLA link monitoring measures the health of…
Read MoreWe added a default Retention Policy for the Telegraf databases. The default Retention Policy can be enabled and configured in the Icingaweb2 Modules Settings under: Configuration > Modules > analytics > Configuration. For NetEye 4.22 we updated the following packages: icingaweb2-module-analytics, icingaweb2-module-analytics-autosetup to version 1.48.2-1
Read MoreWe fixed a wrong behaviour which causes neteye satellite config create to do not work when executed with –tenant parameter. For NetEye 4.22 we updated the following packages: elasticsearch, elasticsearch-autosetup, elasticsearch-neteye-config, filebeat, filebeat-autosetup, filebeat-neteye-config, apm-server, apm-server-autosetup, apm-server-neteye-config, kibana, kibana-autosetup, kibana-neteye-config, logstash, logstash-autosetup, logstash-neteye-config to version 7.15.0_neteye3.37.2-1
Read MoreDuring my experience as a Würth Phoenix consultant, I’ve seen a pretty long list of broken Icinga 2 configurations. Several times, customers have begun a scheduled meeting with something like “Hey mister consultant, ever since the last deploy some objects have stopped being monitored, but I don’t see any errors!”. After some troubleshooting, everything always…
Read MoreWith NetEye 4.22 we released a feature awaited for years: the ability to reach the Elasticsearch API externally, thanks to our NGINX proxy under NetEye. This new feature brings with it a lot of use cases, but what was turning over and over in my head was the automatic process for verification of the blockchains…
Read MoreSometimes you’d just really like to have an overview of what happens to the Events that flow through Tornado. Where do they come from? Did they get stuck somewhere in the Collectors or in Tornado? Which Tornado Actions did they trigger? Gathering all this information from hundreds of log lines across different services (i.e., Tornado…
Read MoreWe fixed a bug in El Proxy, which caused the El Proxy service to not being able to sign new logs after a restart, in the particular case that the last signed log of the blockchain was put in the Dead Letter Queue. For NetEye 4.22 we updated the following packages: elastic-blockchain-proxy, elastic-blockchain-proxy-autosetup to version…
Read MoreSynopsis High impact: Grafana security update Type/Severity Security Advisory: High impact Topic An update for grafana is now available for NetEye 4.22. NetEye Product Security has rated this update as having a security impact of High. Common Vulnerability Scoring System (CVSS) base scores provide additional guidance about a vulnerability and give a detailed severity rating….
Read MoreWe fixed a bug in Tornado which caused rules to not match if the ${item} of the ForEach action was interpolated with other strings. For NetEye 4.22 we updated the following packages: tornado, tornado-autosetup, tornado-common, tornado-neteye-config, tornado-dto, tornado-rsyslog-collector to version 1.18.3-1
Read MoreWe fixed a bug in Tornado which caused Elastic APM to be unable to relate the traces coming from the Tornado Collectors to the traces of the Tornado Engine. For NetEye 4.22 we updated the following packages: tornado, tornado-autosetup, tornado-common, tornado-neteye-config, tornado-dto, tornado-rsyslog-collector to version 1.18.2-2 icingaweb2-module-tornado, icingaweb2-module-tornado-autosetup to version 1.5.0-3 icingaweb2-module-tornadocarbon, icingaweb2-module-tornadocarbon-autosetup to version…
Read MoreScenarioIn a Microsoft Remote Desktop environment, it’s a common need to force the logoff of a hanged user session. The NetEye Command Orchestrator (CMDO) can help us perform this task by executing remote commands through the Icinga2 agent API. There’s a security limitation built into the Command Orchestrator which allows only numeric parameters for executed…
Read More