Are you a user of Jira Service Management Cloud, do you have the premium version and would you like to use the discovery tool to have a scheme where you can automatically receive updates on devices connected to your network? Well, follow this very simple tutorial and you will have a mapping of your network…
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 MoreAs is by now almost a tradition, this year I am again writing a blog post about the SOS JobScheduler. In this blog I’d like to introduce you to some major changes and improvements to the SOS Berlin JobScheduler. As has already been officially announced on the SOS Berlin website, beginning with Release 2.0.0 the…
Read MoreUncertainty is an inherent part of the complex domain of software development. To reduce uncertainty, we made it a part of our custom agile software development methodology. We plan the next sprint for each team by picking the top-most items from the backlog and giving a rough estimate. However, sometimes a new feature request is…
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 MoreThe Monitoring Plugins have been updated to version 2.3.1 and released in beta.Please have a look at the official documentation for the full list of improvements. Before running the update it is necessary to execute the following command to see if there are any previously modified files: rpm -qV monitoring-plugins Output example:S.5….T. d /usr/lib64/neteye/monitoring/plugins/check_time If…
Read MoreWe fixed a bug in Neteye 4.21 that didn’t allow the cmdorchestrator module to edit a command group without changing the name. For NetEye 4.21 we updated the following packages: icingaweb2-module-cmdorchestrator and icingaweb2-module-cmdorchestrator-autosetup to version 0.11.1-1
Read More