End of Life Updates

Created Mar 17, 2026

9 members

17 discussions

This forum is dedicated to all end-of-life and/or end-of-service deprecations occurring at LogicMonitor.

End of Life Updates
LM Logs and LM Inspector SKU Consolidation
LogsEnd of Life Updates
In an effort to provide a more simplified product experience for our customers, LogicMonitor is consolidating the LM Logs and LM Inspector product names and SKUs under a single product name: Log Inspector . Changes Effective October 1, 2026? LM Logs SKUs reach End of Sale , and will no longer be available for quoting, purchase, or renewal. LM Inspector SKUs renamed Log Inspector . Existing customers on LM Logs or LM Inspector SKUs will continue using the same Logs service, and will transition to a Log Inspector SKU at renewal or when purchasing additional log commitments. Minor product UI naming updates will be introduced in upcoming LogicMonitor releases to align the product experience with the new Log Inspector name. Important: This change does not retire LogicMonitor’s Logs functionality. It is a product naming and SKU consolidation only. Why Is LogicMonitor Making This Change? Consolidating LM Logs and LM Inspector under the Log Inspector name will provide a simpler and more consistent customer experience by: Reducing confusion between the existing Logs product names Aligning product, quoting, billing, and documentation terminology Providing clearer positioning for LogicMonitor’s Logs offering Simplifying the management of Logs products across LogicMonitor systems What Does This Mean for You? A more simplified product experience, with: No impact to your current Logs usage or functionality No change to pricing as a result of this update No product migration or configuration changes required No interruption to your existing Logs service You will begin to see the Log Inspector name reflected in the LogicMonitor product UI, renewal documentation, quotes, and billing line items as the consolidation is implemented. Timing October 1, 2026: LM Logs and LM Inspector SKUs reach End of Sale and will no longer be available for new quoting or purchase. Upcoming LogicMonitor releases: Minor product UI naming updates will be implemented. At renewal or when purchasing additional log commitments: Existing Logs customers will transition to the corresponding Log Inspector SKU. What Do You Need to Do? No action is required at this time. Your LogicMonitor account team will coordinate the SKU update with you as part of your renewal, or if you purchase additional log commitments. Questions or Support If you have questions regarding this announcement or would like additional information, please contact your LogicMonitor Customer Success Manager (CSM) or Account Executive (AE). We appreciate your partnership as we continue to simplify and align the LogicMonitor product experience.
Tina ReynoldsAdminPosted 1 week ago
0
End of Life Updates
Apache Groovy 2 Support Ends for MGD Collectors: Milestone Complete
As of September 1, 2026, Collector 39.005 has officially been designated as LogicMonitor's 2026 Minimum General Release (MGD) . With this milestone, Apache Groovy 2 is no longer supported on MGD Collectors . Customers who have not yet upgraded may continue to voluntarily upgrade to Collector 39.005, before the automatic upgrade process begins on October 5, 2026, at 10:00 p.m. PDT . We strongly encourage customers to use this remaining window to ensure their installed LogicModules and NetScans are Groovy 4 compatible, and complete their upgrade before the automatic upgrade begins. For full details, upgrade guidance, and resources, please refer to our original Apache Groovy 2 to Groovy 4 Transition Community Post . Thank you for your continued partnership as we complete the final stage of this Groovy 2 to 4 transition on October 5, 2026!
Tina ReynoldsAdmin1 month ago
0
End of Life Updates
End-of-Life (EOL) for Legacy Versions 5, 6, 7, and 8 for LM Container & Argus is Complete
End of Life Updates
Following our earlier announcement , the End of Life (EOL) for Legacy Versions 5, 6, 7, and 8 for LM Container & Argus was successfully completed on July 31, 2026 . This milestone represents an important step in maintaining a secure, reliable, and modern platform. By retiring these legacy versions, we can continue investing in the latest capabilities, performance improvements, and security enhancements available in current releases. What this means for you Legacy Versions 5, 6, 7, and 8 are no longer supported by LogicMonitor. Engineering and Technical Support will no longer provide assistance for these legacy versions. Customers need to upgrade to the latest supported version 13.2.0 , to continue receiving support, security updates, and product enhancements. Keeping your environment on a supported release helps ensure access to the latest features, improved reliability, ongoing security updates, and the best possible experience with LogicMonitor. If you have questions or need assistance, please reach out to your Customer Success Manager (CSM) or contact LogicMonitor Technical Support . Thank you for partnering with us as we continue to modernize the platform and deliver new innovations.
Tina ReynoldsAdminPosted 2 months ago
0
End of Life Updates
Upcoming End of Life (EOL) for LM APM Synthetics (SYN)
CatchpointAPMEnd of Life Updates
LogicMonitor is announcing the planned deprecation for LM APM Synthetics (SYN) , with a target EOL date of May 31, 2027 . As part of our continued investment in modern, scalable observability solutions, LogicMonitor will standardize synthetic monitoring capabilities on our new Synthetics & Internet Performance Monitoring product. What’s Changing LM APM Synthetics (SYN) will be retired, and will no longer be available following the EOL date of May 31, 2027 Customers currently using SYN will transition to our new Synthetics & Internet Performance Monitoring Existing customers will continue to receive support during the transition period through the EOL date Timing August 3, 2026: End of Quote - No longer available to quote (COMPLETE) September 15, 2026 : End of Sale - No longer available for purchase May 31, 2027 : End of Life (EOL) - Fully deprecated/retired with no further access or support. Why We’re Making This Change This transition enables customers to benefit from a more powerful, scalable, and modern synthetic monitoring platform . Synthetics and Internet Performance Monitoring offers: Global test locations, instead of relying solely on local collectors Filmstrips and playback show exactly where transactions break Broader test types (API, browser, network, etc.) allow you to validate full user journeys, and aren’t limited to basic checks Native in-platform editing eliminates reliance on brittle external scripts, enabling faster updates and reducing maintenance overhead. Cloud-based execution and simplified setup eliminate reliance on collectors and streamline configuration. A modern platform experience built to replace legacy Selenium-based architecture Transition & Customer Support We understand transitions like this require planning, and we are committed to helping customers through the process. Customers can expect: Guidance from your LogicMonitor teams Transition planning assistance Access to training and enablement resources Support throughout the transition timeline ** Please note that historical SYN data will not be migrated as part of the transition. Questions or Support If you have questions regarding this announcement, planning for your transition, or simply require assistance, please contact your Customer Success Manager (CSM), Account Executive (AE), or reach out to the LogicMonitor Technical Support team . We appreciate your continued partnership, and look forward to helping you take advantage of the expanded capabilities available through our new Synthetics & Internet Performance Monitoring product .
Tina ReynoldsAdminPosted 4 months ago
0
Discussion
Tina Reynolds
Admin
Upcoming End-of-Life (EOL) for UIv3 Resources (Including UIv3 Services): August 31, 2026
End of Life UpdatesUIResources
LogicMonitor will soon be deprecating the legacy UIv3 Resources pages ( Including UIv3 Services ). Effective August 31, 2026 , UIv3 Resources & Services will no longer be accessible within the LogicMonitor platform. Customers will continue accessing all Resources & Services functionality through UIv4 Resources & UIv4 Services . What is changing? The legacy UIv3 Resources pages (which includes UIv3 Services) will be retired on August 31, 2026. Customers will continue using UIv4 Resources and UIv4 Services , which already provides equivalent functionality, with no migration effort required. Aside from minor visual and styling differences, the functionality and capabilities remain consistent between UIv3 and UIv4 Resources and Services. In UIv4, Services has been moved from previously being accessed from within Resources, to now being available as a standalone icon in the left navigation menu. Why is LogicMonitor making this change? Transitioning fully from UIv3 Resources & Services to UIv4 allows customers to benefit from: A more modernized and streamlined Resources experience Improved consistency and usability across the LogicMonitor platform Continued enhancements and future innovation within a single UI experience Timing Initial customer notification to current users: June 1, 2026 Official End-of-Life (EOL) for UIv3 Resources (Including UIv3 Services): August 31, 2026 What should customers do next? Customers currently using UIv3 Resources or Services are encouraged to begin familiarizing themselves with UIv4 Resources and Services ahead of the deprecation date. LogicMonitor will continue supporting customers throughout this transition by: Monitoring and addressing any remaining parity gaps Providing updated documentation and FAQs Offering ongoing customer support and enablement resources Questions? If you have questions regarding this announcement or require assistance, please contact your Customer Success Manager (CSM) or reach out to the LogicMonitor Technical Support team . We appreciate your partnership as we continue modernizing and enhancing the LogicMonitor platform experience.
4 months ago
0
Discussion
Sky Donnell
Admin
End of Sale for “On-Demand” Legacy Websites
Following our previous announcement regarding the End-of-Sale (EOS) for On-Demand Legacy Websites (LWM), we want to confirm that as of today, May 06, 2026, this on-demand capability has now been deprecated. As part of our continued platform evolution and focus on delivering more advanced, unified monitoring capabilities, Websites On-Demand is no longer available. If you are currently evaluating alternatives or need guidance on next steps, we encourage you to connect with your Customer Success Manager (CSM) or Account Executive (AE). They can help you identify the best-fit solutions within the LogicMonitor platform to support your ongoing monitoring and digital experience needs.
5 months ago
0
End of Life Updates
UIv3 Dashboards Have Been Deprecated: Tips for the New Dashboard Experience
DashboardEnd of Life Updates
As LogicMonitor continues to evolve the dashboard experience, UIv3 Dashboards have now been deprecated in favor of the new dashboard experience. Dashboards are a critical part of how teams monitor performance, troubleshoot issues, and share insights across the business. Any change to that experience matters. The good news is that transitioning to the new dashboard experience is more straightforward than many users expect. Existing dashboards remain available, core functionality is still there, and the updated experience introduces meaningful improvements that make dashboards easier to use, manage, and share. To help users get up to speed quickly, we’ve put together a short set of videos that walk through the most important updates and show how to make the most of the new dashboard experience. What To Expect From The New Dashboard Experience The transition to the new UI is designed to be as seamless as possible. For most users, the biggest changes are not about rebuilding dashboards from scratch, but about learning a more modern, streamlined way to work. Here are a few practical tips to make the transition easier: Get Familiar With The Updated Layout The overall dashboard structure will still feel familiar, but navigation and actions are now more efficiently organized. Common controls like time range selection, adding widgets, and dashboard actions are easier to access, helping teams move faster in daily workflows. Watch: Navigation and Interface Updates Use Filters To Reduce Dashboard Sprawl One of the biggest improvements in the new dashboard experience is filtering. Instead of maintaining multiple versions of similar dashboards, users can quickly filter by customer, environment, or other criteria, and the full dashboard updates instantly. Saved views make repeat workflows even faster and more consistent across teams. Watch: Dashboard Filters: Improvements and Saved Views Share The Exact View You Want Others To See Collaboration is easier in the new experience. Shared dashboard links can preserve time ranges and applied filters, making it much easier to align teammates, stakeholders, or customers around the same set of data, without extra explanation. Watch: Sharing Dashboards and Enhanced Collaboration Take Advantage Of More Flexible, Query-Driven Analysis The Advanced Metrics widget brings a powerful new way to build dashboards. By using LMQL to define and reuse queries, teams can create more flexible visualizations for troubleshooting, reporting, and customer-specific views, all from the same underlying logic. Watch: Advanced Metrics Widget and Query-Driven Visualization Keep Using The Widgets You Already Know For teams already using Custom Graph, Big Number, and Pie Chart widgets, the good news is that those familiar capabilities remain in place. The main change is a cleaner, more structured configuration experience that makes widget setup and editing easier. Watch: Classic Widgets: Custom Graph, Big Number, and Pie Chart Why This Transition Matters The new dashboard experience is not just a visual refresh. It creates a stronger foundation for faster workflows today and more innovation going forward. With improved filtering, easier sharing, more flexible visualization options, and a more intuitive configuration experience, teams can get more value from dashboards with less effort. The move away from UIv3 Dashboards is an opportunity to simplify dashboard management, improve collaboration, and leverage a more modern experience built for how teams work today. With the right features already in place and guided walkthroughs available for the most important changes, getting comfortable with the new dashboard experience can be quick, practical, and immediately valuable.
Sky DonnellAdminPosted 5 months ago • Last reply 5 months ago
1
End of Life Updates
Upcoming End of Sale (EOS) for “On-Demand” Legacy Websites (LWM): April 30, 2026
End of Life Updates
At LogicMonitor, we are continuously innovating to deliver enhanced monitoring experiences for our customers. As part of this evolution, we are announcing the upcoming End of Sale (EOS) for “On-Demand” Legacy Websites (LWM) . This change begins our transition to LogicMonitor’s recently introduced LM , Uptime , our next-generation website and service monitoring solution. What’s Changing? Effective April 30, 2026 , customers who use Legacy Websites (LWM) in an on-demand basis (not licensed for on your current agreement), will no longer be able to purchase or use the product . Important: This change does NOT impact currently subscribed customers who are licensed for Legacy Websites on your agreement . Why Is This Happening? (Benefits of Transitioning to LM Uptime) Transitioning to LM Uptime , provides you with enhanced website and service monitoring capabilities such as these: Smarter Monitoring: All data points support alerting, with dynamic thresholds, flexible graphing, and full dashboard/widget compatibility. Operational Simplicity: Alert routing, group inheritance, and property management now work just like with devices, reducing support burden and setup time. Service Integration: Uptime checks can be added to Services, linking performance to business outcomes. Future-Readiness: This shift sets the stage for better correlation, reporting, and AI insights across all resources. Timing: Now – April 30, 2026: Customers may continue using Legacy Websites (LWM) under the current on-demand model. April 30, 2026: The End of Sale for On-Demand Legacy Websites (LWM) becomes effective. After this date, the on-demand option will no longer be available for purchase or use. What Do You Need to Do? If you are currently using On-demand Legacy Websites (LWM) , we recommend that you: Familiarize yourself with the enhanced capabilities available in LM Uptime . Plan your transition to LM Uptime ahead of the April 30, 2026 deadline. Connect with your Customer Success Manager or Account Manager to discuss how you can subscribe to LM Uptime. We appreciate your partnership as we continue to modernize and enhance the LogicMonitor platform. Our goal is to ensure you benefit from the most secure, scalable, and innovative monitoring solutions available.
Sky DonnellAdminPosted 7 months ago • Last reply 7 months ago
2
End of Life Updates
Upcoming End of Life (EOL) for API v1 & v2 (New Customers Only): April 30, 2026
End of Life Updates
At LogicMonitor, we are committed to modernizing our platform and ensuring customers benefit from improved performance, security, and long-term scalability. As part of our product lifecycle process, we are announcing the upcoming EOL for API v1 and v2 for new customers only. What’s Changing? LogicMonitor will be deprecating API v1 and v2 for “new” customers only. Effective April 30, 2026, all newly created LM portals will only support LM API v3. API v1 and v2 will remain available for existing customers (no change to existing usage unless otherwise communicated). Why Is This Happening (Benefits of Transitioning to API v3)? This transition ensures that all new customers start on API v3 , our most current and fully supported API framework, delivering: Improved performance and scalability Enhanced security standards Long-term platform stability and on-going support Access to the latest API features, capabilities and enhancements Timing: Now until April 30, 2026: Legacy and current versions will both remain available to new customers during this transition period April 30, 2026: API v1 and v2 will be fully deprecated for new customers What Do You Need to Do? If your onboarding workflows, automation scripts, integrations, or tooling currently leverage API v1 or v2 to create new portals, you must update them to API v3 before April 30, 2026 . Recommended Next Steps Audit existing automation and provisioning scripts Identify dependencies on API v1 or v2 Plan and validate migration to API v3 Coordinate internally to ensure readiness before the deadline If you have questions or need assistance, please reach out to your Customer Success Manager or contact LogicMonitor Technical Support . We appreciate your partnership as we continue to evolve and strengthen the LogicMonitor platform.
Sky DonnellAdminPosted 7 months ago
0
End of Life Updates
Upcoming End of Life (EOL) for Legacy Versions 5, 6, 7, and 8 for Legacy LM Container & Argus: July 31, 2026
End of Life Updates
At LogicMonitor, we’re continually working to ensure customers have a consistent experience across the platform as it evolves. As part of our regular product lifecycle process, we’re announcing the upcoming deprecation for legacy versions 5, 6, 7, and 8 for LM Container and Argus . What’s changing? LogicMonitor will be deprecating legacy versions 5, 6, 7, and 8 for LM Container and Argus . After July 31, 2026 , these legacy versions will no longer be available for use within the LogicMonitor platform. What does this mean for you? Customers already running more current versions will not be impacted Customers using legacy versions 5, 6, 7, or 8 for LM Container or Argus will need to upgrade to a more current version before the EOL date All monitoring and functionality will continue in current supported versions Timing: Now – July 31, 2026: Legacy and current versions will both remain available during this transition period July 31, 2026: Legacy versions 5, 6, 7, and 8 for LM Container and Argus will be fully deprecated What do you need to do? If you’re currently using one of the affected legacy versions , please plan your for upgrade to a more current version prior to the EOL date . If you have questions or need assistance, please reach out to your Customer Success Manager or contact LogicMonitor Technical Support . We appreciate your partnership as we continue to modernize the platform.
Sky DonnellAdminPosted 8 months ago
0
End of Life Updates
Upcoming End of Life (EOL) for UIv3 Dashboards: April 30, 2026
End of Life UpdatesDashboard
LogicMonitor will soon be deprecating the legacy UIv3 Dashboards experience. Dashboards will continue to be fully available and supported in UIv4, which many customers are already using today. This change allows us to provide a consistent, modern dashboard experience, and focus future improvements in a single interface. We know changes like this can require planning, so we wanted to share details early and clearly. What’s changing? UIv3 Dashboards will be deprecated on April 30, 2026 After that date, dashboards will be accessed exclusively through UIv4 What does this mean for you? No loss of dashboards or data: Existing dashboards are already available in UIv4 No migration work required: Layouts and core functionality remain equivalent A consistent experience: All future dashboard improvements will be delivered in UIv4 going forward Timing: Now – April 30, 2026 : UIv3 and UIv4 Dashboards are both available April 30, 2026 : UIv3 Dashboards will be fully deprecated What do you need to do? If you’re already using UIv4 Dashboards, no action is required. If you’re still using UIv3 , begin spending time in UIv4 ahead of the retirement date so that you and your teams are familiar with the experience, prior to the deprecation date. If you have questions or need assistance, please reach out to your Customer Success Manager or contact LogicMonitor Technical Support . We appreciate your partnership as we continue to modernize the platform.
Sky DonnellAdminPosted 8 months ago
0
End of Life Updates
Apache Groovy 2 End-of-Life Milestone Public Announcement
End of Life Updates
In support of Apache Groovy’s end of support for Apache Groovy 2, 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 The above timeline is based on current information, and dates may be subject to change. Any changes will be shared accordingly. Migration Updates - To determine which Groovy version is used for module execution, please reference the Collector Versions table . As we continue to refine and improve Collector performance, it's important to note that EA 39.100 is expected to perform similarly to previous Collector versions, providing the consistency many customers are familiar with. While GD 39.000 included specific performance improvements, it's important to note that this release was not representative of the standard Collector baseline. That said, we’re continuously working to incorporate enhancements into future versions to deliver consistent and reliable performance for all customers. Through August, MGD Collectors will utilize Groovy 2 as the default scripting engine, while Groovy 4 remains available for early adopters. This phased approach allows us to fine-tune Groovy 4 based on real-world feedback, while also giving customers ample time to test and migrate their custom modules with confidence. We’re actively exploring performance enhancements, and will continue to expand and refine support for Groovy 4 over time to ensure an optimal experience. 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 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-228-release-notes#h-modules 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 .
Suzanne ShawAdminPosted 2 years ago
0

LM Logs and LM Inspector SKU Consolidation

Apache Groovy 2 Support Ends for MGD Collectors: Milestone Complete

End-of-Life (EOL) for Legacy Versions 5, 6, 7, and 8 for LM Container & Argus is Complete

Upcoming End of Life (EOL) for LM APM Synthetics (SYN)

Upcoming End-of-Life (EOL) for UIv3 Resources (Including UIv3 Services): August 31, 2026

End of Sale for “On-Demand” Legacy Websites

UIv3 Dashboards Have Been Deprecated: Tips for the New Dashboard Experience

Upcoming End of Sale (EOS) for “On-Demand” Legacy Websites (LWM): April 30, 2026

Upcoming End of Life (EOL) for API v1 & v2 (New Customers Only): April 30, 2026

Upcoming End of Life (EOL) for Legacy Versions 5, 6, 7, and 8 for Legacy LM Container & Argus: July 31, 2026

Upcoming End of Life (EOL) for UIv3 Dashboards: April 30, 2026

Apache Groovy 2 End-of-Life Milestone Public Announcement