Icinga Director Now Responsive During Configuration Deployments
Previously, users were unable to interact with Icinga Director while configuration deployments were running. Any attempt to access the interface or API would be blocked until the deployment completed, causing unnecessary delays in daily operations.
This fix resolves the blocking issue, allowing users to continue working with Director even during active deployments. You can now make changes, query configurations, and use the API without waiting for deployment processes to finish.
List of updated packages
To solve the issue mentioned above, the following packages have been updated for NetEye 4.46:
icingaweb2-module-director, icingaweb2-module-director-autosetup,icingaweb2-module-director-configurator version 1.11.4_neteye1.40.8-1
Practical lessons learned from real-world alert routing, automation, and integrations Introduction As mentioned at the end of Part 1, let's continue exploring practical use cases and real‑world solutions for Jira Operations alert handling and enrichment. NetEye, Icinga, and Jira Ops Read More
Fix: monitoring links from the Event Overview When opening a link from the Event Overview page, the monitoring URL was supposed to be translated into the corresponding IcingaDB link. The translation was only handled on a simple click, though, so Read More
Improve visibility of Feature command state icons Feature command state icons and captions were difficult to see against the white background in the UI. To improve readability and accessibility, we updated the icon and caption colors to provide stronger contrast Read More
Important: Keycloak security update Type/Severity NetEye Product Security has rated this update as having a high security impact. Topic An update for the keycloak packages is now available for NetEye 4. Security Fix for NetEye 4.48 26.6.2_neteye1.40.0-1 Summary This vulnerability allows an attacker Read More
Fix HEAD HTTP method not supported We resolved a compatibility issue affecting HEAD requests to NetEye endpoints. These requests could previously time out because the method was not fully supported by the underlying architecture. As a result, some procedures could Read More