Deprecation of support for vendor end-of-life Linux versions
- Effective Date: February 2027
- Announcement Date: November 2026
| Linux distribution | Versions affected | Vendor lifecycle note |
|---|---|---|
| Amazon Linux | Amazon Linux AMI releases from 2012.03 through 2018.03 | Amazon Linux AMI, also known as Amazon Linux 1, reached end of life on December 31, 2023. |
| CentOS Linux | CentOS 6 and 7 | CentOS 6 security support ended November 30, 2020. CentOS 7 security support ended June 30, 2024. |
| Fedora Linux | Fedora 31 through 42 | Fedora 31 through 42 have reached end of support. Fedora 42 security support ended May 27, 2026. |
| Oracle Linux | Oracle Linux 6 and 7 | Oracle Linux 6 has completed Extended Support. Oracle Linux 7 has completed Basic/Premier Support but remains eligible for Extended Support through July 31, 2029. |
| Red Hat Enterprise Linux (RHEL) | RHEL 6 and 7 | RHEL 6 has completed Extended Life Cycle Support. RHEL 7 completed Maintenance Support in June 2024, although Extended Life Cycle Support remains available through May 31, 2029. |
| SUSE Linux Enterprise Server (SLES) | SLES 11 SP4 | SLES 11 SP4 General Support and Long Term Service Pack Support have ended. |
| Ubuntu Linux | Ubuntu 14.04 LTS, 16.04 LTS, 18.04 LTS, and 20.04 LTS | Standard maintenance/security support has ended for these releases. Some releases may remain covered by Canonical's extended support offerings. For example, Ubuntu 20.04 ESM is available beyond its standard support period. |
| Debian Linux | Debian 8 through 11 | Standard Debian security support and LTS have ended for these releases. Some versions may remain eligible for third-party Extended LTS services. Debian 11 LTS ended August 31, 2026. |
Retirement of Classic Alert Policies, Service Desk Tickets, and Notifications
Classic Alert Policies
- Effective Date: January 2027
- Announcement Date: October 2026
As part of our ongoing platform modernization efforts, Classic Alert Policies (Setup → Setup → Alerts) will be retired with the January 2027 release.
Customers are encouraged to migrate to V2 Alert Policies, Service Desk Tickets, and Notification Templates, which offer:
- A modern and improved user experience
- Consistent filtering powered by OpsQL across the platform
- Simplified alert actions and policy management
- Enhanced usability and maintainability
To access the new experience, navigate to Setup → Account → Alert Policies.
Until the end of December 2026, users can continue using Classic Alert Policies by clicking Back to Previous Experience in the top-right corner of any New Alert Policy page.
With the January 2027 release, the Setup → Setup → Alerts menu and the Back to Previous Experience link on the New Alert Policies page will be removed.
Classic Service Desk Tickets
New Service Desk Tickets is the default experience. Navigate to Command Center → Tickets.
Until the end of December 2026, users can continue using Classic Service Desk Tickets by clicking Back to Previous Experience in the top-right corner of the New Service Desk Tickets page.
With the January 2027 release, the Back to Previous Experience link on the New Service Desk Tickets page will be removed.
Classic Notifications
- Effective Date: January 2027
- Announcement Date: October 2026
Classic Notifications, accessed via Setup → Setup → Notifications, will be retired with the January 2027 release. Users must navigate to Setup → Account → Notification Templates to access the new notification templates for alerts, Service Desk, and process definitions, which provide an enhanced user experience and improved functionality.
Until the end of December 2026, users can continue accessing Classic Notifications from the Setup → Setup → Notifications menu or by clicking Back to Previous Experience in the top-right corner of New Notification Templates.
Navigation
| Feature | Old UI Navigation | New UI Navigation |
|---|---|---|
| Alert Policies | Setup → Setup → Alerts | Setup → Account → Alert Policies |
| Service Desk Tickets | Command Center → Tickets | Command Center → Tickets |
| Notifications | Setup → Setup → Notifications | Setup → Account → Notification Templates |
Previous Announcements
These retirement plans were previously communicated in the following deprecation notices:
Deprecation of Classic application
- Effective Date: December 2026
- Announcement Date: October 2026
Effective from December 2026, OpsRamp will officially deprecate support for IBM Storwize Classic application.
New installations are not allowed, but existing integrations will continue to work.
Recommendation
Use IBM FlashSystem for all new integrations and future configuration.Deprecation of the Infrastructure → Resources Page
- Effective Date: December 2026
- Announcement Date: October 2026
To provide a faster and more streamlined resource discovery experience, OpsRamp is deprecating the legacy Infrastructure → Resources page.
The page will be replaced by Infrastructure → Search, which offers the new V2 user experience and supports OpsQL-based queries. This enhanced search experience helps users quickly find and filter resources across their environments.
What Is Changing?
| Current Page | Replacement Page |
|---|---|
| Infrastructure → Resources | Infrastructure → Search |
The legacy Infrastructure → Resources page is being removed in the December 2026 release. After its removal, customers should use Infrastructure → Search to find resources.
Benefits of the New Experience
The Infrastructure → Search page provides:
- A modern v2 user experience
- Faster resource identification
- Flexible filtering through OpsQL-based search queries
- Integration-based resource categorization
Customer Action Required
Customers should begin using Infrastructure → Search before the December 2026 release. Customers should also update internal documentation and training materials that currently reference Infrastructure → Resources.
This change affects only how customers access and search for resources. Existing resources and configurations are not affected.
Legacy Account Management Pages
- Effective Date: December 2026
- Announcement Date: October 2026
To streamline account administration and provide a more consistent user experience, OpsRamp is deprecating the legacy account management pages available under Setup → Setup → Accounts. These capabilities are already available in the modern Setup → Account navigation, and customers should begin using the new locations going forward.
What’s Changing?
The following legacy pages under Setup → Setup → Accounts will be removed:
- Partner Details
- Clients
- User Groups
- Users
- Roles
- Permission Sets
- Custom Branding
- Client Checklist
- Lookup Two-Factor Key
No functionality is being removed. These capabilities have been consolidated under the Setup → Account navigation to improve usability and administration.
New Navigation Paths
The legacy account management pages have been moved to the following locations under the modern Setup → Account navigation:
| Legacy Page | New Location |
|---|---|
| Partner Details | Setup → Account → Settings (Visible in Partner context) |
| Clients | Setup → Account → Settings (Visible in Client context) |
| Users | Setup → Account → Users and Permissions |
| User Groups | Setup → Account → Users and Permissions |
| Roles | Setup → Account → Users and Permissions |
| Permission Sets | Setup → Account → Users and Permissions |
| Custom Branding | Setup → Account → Settings → Branding |
| Lookup Two-Factor Key | Setup → Account → Settings → Security |
Customer Action Required
Customers are encouraged to start using the new navigation paths listed above. Existing functionality remains unchanged; only the access location has been consolidated under the Setup → Account section.
Benefits
-Simplified account administration experience
-Centralized access to account settings and user management
-Improved navigation consistency across the platform
-Reduced dependency on legacy account management pages
Removal
The legacy pages under Setup → Setup → Accounts will be removed in the December 2026 release. Customers should update any internal documentation, operational procedures, or training materials to reference the new navigation paths before the legacy pages are retired.
Note: This change does not impact existing configurations, users, roles, permission sets, branding settings, or security settings. Only the navigation path has changed.
Retirement of Monitoring v1 Pages
- Effective Date: December 2026
- Announcement Date: October 2026
As previously announced, OpsRamp has been transitioning customers from the Monitoring v1 pages to the v2 Monitoring experience. With the December 2026 release, the remaining Monitoring v1 pages will be retired.
- Setup > Setup > Resources
- Setup > Setup > Monitoring
Existing monitoring configurations will be migrated to their corresponding v2 locations. Device Management Policies will be replaced by Template-Based Alert Definitions and Resource Groups. Assignments for jobs, knowledge base articles, credentials, and custom attributes must be managed through Infrastructure > Groups
Customers should begin using the v2 Monitoring pages and update any internal procedures, training materials, or documentation that reference the legacy Monitoring navigation. After the December 2026 release, the Monitoring v1 pages will no longer be available.
Previous Announcements
This change was communicated previously through the following release notes and deprecation notices:
Movement of Features to Alternative Locations
Transition from Device Management Policies to Template-Based Alert Definitions
Explore Template-Based Alert Definitions Before the Transition
If you would like to explore the new Template-Based Alert Definitions before the December 2026 rollout, contact OpsRamp Support. We can enable the v2 Monitoring experience for one of your clients and migrate all existing Device Management Policies for that client to the new Template-Based Alert Definitions page.
This early-access option allows you to experience the new functionality, validate your migrated configurations, and become familiar with the v2 workflow before the Monitoring v1 pages are retired in December 2026.
End of Support for Linux Agent on 32-bit Operating Systems
- Effective Date: November 2026
- Announcement Date: September 2026
Support for the Linux Agent on 32-bit operating systems will be discontinued from effective date. After this date, 32-bit Linux platforms will no longer receive agent updates, security fixes, or technical support.
Deprecation of Classic Adapters templates
- Effective Date: November 2026
- Announcement Date: September 2026
After the Effective Date, OpsRamp will officially deprecate support for the following templates.
Click here to see the list of templates.
- ActiveMQ - API
- CouchDB1 - Statistics
- CouchDB2 - Statistics
- FTP Template
- FTP Template Monitor
- Glassfish JVM Template
- Glassfish Thread,Memory,Sessions Template
- Glassfish Transaction, Classes, System Stats Template
- HBase Master JVM Template
- HBase Master Performance Template
- HBase Regionserver JVM Template
- HBase Regionserver Template
- HBase Sample Template
- HDFS DataNode Template
- HDFS DataNode Template Monitor
- HDFS NameNode Template
- Jetty JVM Template
- Jetty Template
- Lighttpd Performance Template
- Nginx Performance Template
- Nginx Statistics - v2
- RADIUS Authentication Status Check
- RabbitMQ - Nodes Performance and Health
- RabbitMQ - Overall Statistics
- RabbitMQ - Overall Statistics - v2
- RabbitMQ - Queues Statistics
- RabbitMQ Aliveness Check Status
- Resin CacheStore - ClusterServer Template
- Resin Memory - Web App Template
- Resin ThreadPool - Server Template
- TomEE Microprofile Template
- TomEE Plume Template
- TomEE Plus Template
- TomEE Webprofile Template
- TomEE Microprofile JVM Template
- TomEE Plume JVM Template
- TomEE Plus JVM Template
- TomEE Webprofile JVM Template
- Zookeeper Replicated JVM Template
- Zookeeper Replicated Template
- Zookeper Standalone JVM Template
- Zookeper Standalone Template
Deprecation of Assignment of Jobs, Knowledge Base Articles, Credentials, and Custom Attributes from Device Management Policy
- Effective Date: December 2026
- Announcement Date: September 2026
After the Effective Date, these assignment actions will no longer be available under Setup → Setup → Resources → Device Management Policy.
- Assign Knowledge Base Articles
- Assign Jobs
- Assign Credentials
- Assign Custom Attributes
Going forward, use Infrastructure → Groups to manage these assignments. This change eliminates duplicate functionality, simplifies administration, and accelerates the transition away from the legacy user interface.
This restriction applies only to new Device Management Policies. Existing Device Management Policies that use these assignment actions will continue to function as configured, and the system will retain their current assignments. Customers do not need to take any immediate action for existing policies.
The following actions remain supported under Setup → Setup → Resources → Device Management Policy.
- Assign Monitoring Templates
- Assign Availability Rules
These capabilities will remain available until we complete the transition to Setup → Account → Monitoring → Alert Definitions → Template Based Alert Definitions, as described in the previously announced deprecation notice. For more information, refer to Transition from Device Management Policies to Template-Based Alert Definitions.
Recommendation
Customers are encouraged to use Infrastructure → Groups for all new assignments of Knowledge Base Articles, Jobs, Credentials, and Custom Attributes. Future enhancements for these capabilities will be delivered through the Groups experience.Meraki Integration Transition Notice
- Effective Date: January 2027
- Announcement Date: August 2026
To improve scalability for large enterprise deployments, future investment for the OpsRamp Meraki integration will focus on the Gateway based Meraki integration. The current SaaS based integration has known scalability limitations due to Cisco Meraki’s API rate limit of 100 API requests per second per source IP address. The Gateway based Meraki Integration architecture overcomes this limitation by distributing API calls across Gateways, enabling better scalability and performance.
What does this mean for customers?
Existing Customers
- Existing Meraki SaaS integrations will continue to be supported.
- Existing integrations can continue to be updated or deleted.
- From August release, creation of new Meraki SaaS integrations will no longer be supported.
- Customers requiring additional Meraki integrations must use the Gateway based Meraki Integration.
New Customers
- The Meraki SaaS integration will no longer be available for new deployments.
- All new Meraki integrations must be deployed using the Gateway based Meraki Integration.
Future Enhancements
- All new features, enhancements, and monitoring capabilities for Meraki will be delivered only through the Gateway based monitoring integrations 2.0.
- Customers are encouraged to migrate to the Gateway based Meraki Integration to benefit from future functionality and improved scalability.
Existing SaaS Integration
The existing SaaS integration will continue to be supported for current customers till 31-JAN-2027.
See Meraki and Working with Cisco Meraki for more details.
Transition from Device Management Policies to Template-Based Alert Definitions
- Announcement Date: August 2026
- Effective Date: December 2026
As announced earlier in the 2026.04-U1 (April 2026), OpsRamp is moving to the v2 Monitoring UI. Existing Device Management Policies (Setup -> Setup -> Resources -> Device Management Policies) will no longer be visible. OpsRamp will migrate all policies to two new locations.
For newly onboarded customers, OpsRamp has shown the new Template Based Alert Definition by default since the January 2026 release. For existing customers, OpsRamp will stop showing Device Management Policies and migrate the existing policies to new Template Based Alert Definitions and Resource Groups.
See Template-Based Alert Definitions document for more details.
Deprecation note of Classic application
- Effective Date: September 2026
- Announcement Date: July 2026
OpsRamp will officially deprecate support for the Dell XtremIO Classic application.