Notice for Upcoming Deprecation of Websites, Reports, and Settings pages from legacy UI
Because LM is consistently working towards providing an exceptional experience for our customers, starting on April 30, 2025, we are streamlining our platform and will be removing access to the Websites, Reports, and Settings pages in our legacy UI. The new UI will enhance performance and the overall user experience for our valued customers, while also strengthening security as well. Action Required: To minimize disruption to your workflows, by April 30, 2025, you will need to begin to use LM’s new UI for enhanced features and a more intuitive interface. Note: The Dashboards and Resources pages within the legacy UI will continue to be available. Further communication regarding the future of these pages will be forthcoming. Please see the Release Notes for additional details, and if you have questions or require assistance during this process, please contact our Support team or your Customer Success Manager.Apache Groovy 2 End-of-Life Milestone Public Announcement
In support of Apache Groovy’s end of support for Apache Groovy 2.4, the current version being used by LogicMonitor, and transitioning to the new version (Apache Groovy 4), LogicMonitor is announcing the upcoming significant lifecycle milestone dates. Groovy is the primary LogicMonitor language for modules employing script or batch script collection methodologies. Affected Modules Modules Script and batch script NetScan Groovy Scripts that are not Apache Groovy 4 compatible Why the Change? Apache Groovy 2, the current version LogicMonitor uses, is no longer actively supported by the Apache Software Foundation. Therefore, to maintain support, mitigate security risks, and maintain a strong security posture, LogicMonitor is migrating to Apache Groovy 4. Apache Groovy 2 - Key Milestone Timeline Migration Path To ensure services remain unaffected, verify compatibility with Apache Groovy 4 as soon as possible. Failure to complete this step will result in a loss of total functionality. Compatibility Verification Steps Official Modules Where appropriate, LogicMonitor will provide Apache Groovy 4 compatibility updates for official modules. Customers should follow their established change management control processes to implement the updates. For more information, see LogicMonitor Provided Modules Groovy 4 Migration in the product documentation. Unofficial Modules (Customer or community-created LogicModules) For any custom or community-scripted LogicModules, customers must test their modules to ensure compatibility, and make the appropriate updates. Customers should follow their established change management control processes to implement the updates. For more information, please refer to LogicMonitor’s product documentation for Custom Module Groovy Migration Validation. Enhanced Script NetScans Where appropriate, LogicMonitor has provided Groovy 4 compatibility updates for Enhanced Script NetScans. Customers should follow their established change management control processes to implement the updates. For more information, see the Enhanced Script NetScans Now Groovy 4 Compatible section in the v.214 Module Release Notes. Collector Updates To minimize disruption in monitoring, before updating Collectors to version 37.100 or later, customers must first verify Module compatibility with Apache Groovy 4. Supporting Materials Modules Management Collector Release Notes Timeline | LogicMonitor Collector Versions | LogicMonitor Embedded Groovy Scripting | LogicMonitor Scripted Data Collection Overview | LogicMonitor Apache Groovy 4: New Features - Release notes | LogicMonitor Known Issues | LogicMonitor Frequently Asked Questions (FAQ) What happens to customized, custom, or community-created modules? Prior to upgrading to collectors that no longer support Groovy 2, customers will need to test their customized or custom written modules, and make the necessary updates for any compatibility issues. When available, LogicMonitor will provide documentation on how customers can test customized modules, as well as all known issues. How might I start testing my modules for Apache Groovy 4 compatibility? Custom Module Groovy Migration Validation Known Issues: https://www.logicmonitor.com/release-notes/v-205-release-notes https://www.logicmonitor.com/release-notes/v-204-release-notes How will officially supported modules be impacted by this change? All official LogicMonitor-provided modules will be compatible with Apache Groovy 4, and will be tagged ‘groovy4’ as available. How can I tell which modules are supported or not? In the ‘My Modules Toolbox’, under the Support column, please note those marked ‘official’, which will indicate those modules which will continue to be maintained by LogicMonitor. Modules that are no longer maintained will be marked as ‘deprecated’. Why did I receive this customer communication, as I usually receive this type of information from LogicMonitor Release Notes? At LogicMonitor, we are customer-obsessed, and are committed to helping ensure a smooth transition during this major change in our Collectors. Where might I get help if I need more time or resources to test or update custom modules? LogicMonitor Professional Services is available to assist with testing and updating customer LogicModules at a cost. Your Customer Success Manager (CSM) will need to facilitate a Statement of Work (SOW) agreement for the proposed LogicModules and effort needed to make the updates. What happens if I have made script customizations to officially supported modules? You will have to either update to the verified compatible module versions or verify the compatibility of your customizations. What happens if I have updated a module to the latest version, but I am still experiencing issues? Please contact/open a ticket with the LogicMonitor Technical Support Team. What if I have a question that is not covered here? Please reach out to your LogicMonitor Customer Success Manager (CSM) or open a ticket with the LogicMonitor Technical Support Team.
