OpsRamp Release Policy

Introduction

OpsRamp follows a structured release upgrade policy to ensure timely and organized updates for its product components, including the SaaS Platform, Agent, Gateway, Web Services Monitoring (Synthetics), and Content Releases. The policy emphasizes compatibility, customer validation, and proactive communication to enhance operational efficiency, improve user experience, and maintain system security.

Key Elements of the Release Policy

Feature Upgrades: Enhancements to functionality and user experience.
Bug Fixes: Resolution of known issues to improve platform stability.
Security Updates: Critical patches for system safety and compliance.

Advantages of Our Policy

Predictability: Defined schedules for major and minor releases allow for effective planning of maintenance and updates.
Enhanced Stability: Restricting operating system patches to major releases minimizes the likelihood of unexpected issues.
Swift Security Response: Critical vulnerabilities are resolved promptly, reducing exposure to potential threats.
Rigorous QA Process: Each critical patch undergoes meticulous testing to ensure compatibility and optimal performance.

Release Cadence

OpsRamp adopts a predictable release cadence:

Every 6 Months: Collector (Agent and Gateway) major releases for compatibility. Follow N-2 compatibility, encouraging upgrades to the latest versions
Every 2 Months: Collector (Agent and Gateway) minor releases for application-level updates.
Every 4 Weeks: Platform releases for feature upgrades and bug fixes.
Every Week: Integration updates, including monitoring templates and improvements.
On-demand: Hotfixes for critical security issues.

Platform Release Policy

The Platform Release Policy ensures regular updates to the SaaS platform, focused on improving functionality, stability, and security.

Feature Upgrades: Add new tools and capabilities to streamline IT operations and enhance the user experience.
Functionality Enhancements: Optimize features based on customer feedback and evolving industry standards.
Bug Fixes: Resolve issues to improve platform stability, reliability, and security.

Release Type	Frequency	Notification
Platform Releases	Every 4 weeks	1 week before via CSTM and System Health portal

Agent Release Policy

The Agent Release Policy ensures compatibility and functionality of agents through major and minor updates. Following are the release scope and schedule.

Release Type	Scope	Frequency	Notification
Major Releases	Including major functionality, security updates of agents through major updates	Every 6 months	1 week before via CSTM
Minor Releases	Including hot fixes needed for system stability or security	Every 2 months	1 week before via CSTM

Gateway Release Policy

The Gateway Release Policy focuses on OS patching, critical security updates, and application-level improvements to ensure a stable and secure environment. Following are the release scope and schedule.

Release Type	Scope	Frequency	Includes OS Patches	Notification
Major Releases	including all OS patches, security updates, and performance enhancements	Every 6 months	Yes	1 week before via CSTM
Minor Releases	focusing on application-level updates without OS patches to ensure stability	Every 2 months	No	1 week before via CSTM
Critical Patches	Any Global CVE catalog ratings of 7 and above which impact our system	As needed	Yes	Post-release notification via CSTM

Synthetics Release Policy

The Synthetics Release Policy governs updates for web services monitoring through Public and Private Collectors. Following are the release scope and schedule.

Collector Type	Scope	Frequency	Notification
Public Collector	pgraded during platform releases to ensure consistency and reliability	Aligned with platform	Part of plarform release schedule
Private Collector	Managed separately and updated based on customer-specific needs	Custome-specific	Based on customer agreements

Content Release Policy

The Content Release Policy ensures seamless integration with third-party systems and regular updates for monitoring templates.

New Integrations: Add support for additional IT and cloud systems.
Enhancements: Improve performance and reliability of existing integrations.
Bug Fixes: Resolve issues affecting integration performance.

Collector Type	Frequency	Notification
Integration Release	Weekly	Post-release notification via CSTM

Older Versions and Compatibility

To maintain high performance and security, OpsRamp follows a clear compatibility policy:

Unsupported Older Versions: Older versions are not maintained after new releases. Customers must upgrade to continue receiving technical support.
Version Compatibility (N-2): Only the current version (N) and the two preceding versions (N-2) are supported.
Customer Responsibility: Customers are expected to review and update configurations to ensure compatibility with new releases.

Example: If the latest version is 14.0, versions 12.0, 13.0, and 14.0 are supported. Versions older than 12.0 are considered unsupported.

Deprecated Features

OpsRamp provides advance notice of at least one quarter before deprecating any features. These features may either be discontinued or replaced with alternative solutions. While every effort is made to avoid deprecating actively used features, OpsRamp retains the right to modify or remove features at its discretion without prior notice. Upcoming deprecations are detailed in the Deprecations section of the OpsRamp portal.

Communication Policy

Notification Type	Details
Release Notes (Internal)	Shared with Customer Success teams 1 week before upgrades.
Pod Upgrade Schedule (Internal)	Shared with Customer Success teams 2 weeks before deployment.
Pod Upgrade Notification (External)	Posted on System Health page 1 week before release; email notifications for subscribers.
Release Notes (Customer)	Published on the documentation portal after the first production pod upgrade.

Disclaimer

OpsRamp reserves the right to modify its upgrade policy as part of its continuous efforts to improve customer service.