Fix unnecessary action retries in Tornado’s Smart Monitoring component We fixed a bug affecting Tornado in NetEye 4.45 for a specific edge case in Tornado’s Smart Monitoring component that was causing unnecessary system overhead and log bloat. Specifically, when Tornado attempted to perform a “check result” in Icinga2 for a host that had been disabled…
Read MoreFix contract list option wrongly disabled in SLM reports We fixed a bug affecting the SLM reporting in NetEye 4.45. The issue occurred during the modification of a report, when one of the contracts in the list could not be selected because the corresponding report would have been empty. In that case, the selection of…
Read MoreNetEye’s SLM module is tightly coupled to Icinga 2’s legacy monitoring backend, which was removed upstream with the introduction of IcingaDB. Official documentation exists that describes how to migrate configuration files written using the old syntax, but it’s incomplete and – more importantly – it doesn’t explain how to migrate PHP code that depends on…
Read MoreBug Fix in Tornado Module We solved an issue in Tornado’s rule configuration where the action_name field in director actions was being cleared after saving and deploying. When users created a rule with a director action and filled in both action_name and action_payload, the action_name value would disappear upon returning to the rule configuration. This…
Read MoreScenario NetEye 4 is a comprehensive monitoring platform which natively supports Business Processes. A Business Process is an abstract view of a customer’s business from the Application point of view. Usually, it’s a collection of Icinga 2 checks aggregated by “AND, OR, At Least” logic in order to monitor whether a Business Application is really…
Read More