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.
Release Cadence
OpsRamp adopts a predictable release cadence to deliver regular updates:
- Every 4 weeks: Platform releases for feature upgrades and bug fixes.
- Every 6 months: Collector (Agent and Gateway) releases for major versions ensuring compatibility.
- Every 1 week: Integration releases, including monitoring templates and integrations, are delivered weekly and are treated separately from platform upgrades.
- On-demand: Hotfixes for critical security issues.
Release Components
SaaS Platform
OpsRamp follows a structured approach to delivering regular feature upgrades, functionality enhancements, and bug fixes to ensure the platform remains robust, innovative, and secure. These updates are designed to address customer needs, improve operational efficiency, and enhance the overall user experience.
- Feature Upgrades: Introduce new tools, capabilities, and improvements to streamline IT operations and expand the platform's functionality.
- Functionality Enhancements: Optimize existing features based on customer feedback and evolving industry standards to ensure seamless performance.
- Bug Fixes: Resolve identified issues to improve stability, reliability, and security, ensuring smooth operation of all platform components.
Agent and Gateway Releases
Both the Agent and Gateway follow a half-yearly release cycle, ensuring that they remain in sync with the SaaS Platform updates.
- Agent Releases: Major releases every 6 months with enhancements and bug fixes. Customers are expected to upgrade to the latest versions (N-2 compatibility).
- Gateway Releases: Similar half-yearly release cycles as the Agent, ensuring compatibility and functionality improvements.
Web Services Monitoring (Synthetics)
Web Services Monitoring is divided into two modes:
- Public Collectors: Upgraded during regular platform releases.
- Private Collectors: Managed separately on customer gateways and upgraded based on customer-specific needs.
Content Releases
OpsRamp also regularly updates integrations to ensure seamless connectivity with third-party systems. These updates include new integrations, improvements to existing integrations, and bug fixes. Integration updates are typically released as part of the weekly content releases. These updates are documented in the Release Notes.
- New Integrations: New integrations with popular IT and cloud systems.
- Improvements to Existing Integrations: Enhancements and optimizations to improve performance and reliability.
- Bug Fixes: Resolution of issues impacting integration performance.
Older Versions and Compatibility
To ensure high standards of performance and security, OpsRamp maintains a clear policy regarding older versions and compatibility.
Unsupported Older Versions: Once a new release is deployed, older versions of the SaaS platform, Agent, and Gateway are no longer maintained or supported. Customers are encouraged to upgrade to the latest version to take advantage of new features and continue receiving technical support.
Version Compatibility Policy: OpsRamp follows an N-2 compatibility policy, meaning the current version (N) and the two preceding versions are supported. Customers using versions older than N-2 must upgrade to a supported version before submitting support requests.
Customer Responsibility: Customers should review and update their custom configurations to ensure compatibility with new releases. Upgrading to the latest version guarantees access to new features, critical fixes, and security updates.
Example: If the latest release is 14.0, OpsRamp supports versions 12.0, 13.0, and 14.0. Any version older than 12.0 is considered unsupported. By following this policy, OpsRamp ensures that customers benefit from the latest innovations while maintaining a stable and secure IT environment.
Deprecated features
Deprecated features are announced at least one quarter in advance. These features are either discontinued or replaced by alternative implementations. While OpsRamp avoids deprecating features actively in use, the company reserves the right to modify or remove features without prior notice. Future deprecations are documented in the Deprecations section of the OpsRamp portal.
Release Types and Frequency
| Release Type | Scope | Frequency | Notification |
|---|---|---|---|
| Platform Releases | Feature upgrades, bug fixes | Every 4 weeks | 1 week before via CSTM and System Health portal |
| Base Releases | Major versions for compatibility | Every 6 months | 1 week before via CSTM and System Health portal |
| Integration Releases | New integrations and enhancements | Every week | Post-release notification via CSTM |
| Hotfixes | Critical fixes for security | On-demand | Post-release notification via CSTM |
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 the System Health page 1 week before release, with email notifications for subscribers. |
| Release Notes (Customer) | Published on the documentation portal after the first production pod upgrade. |
Related links
Disclaimer
OpsRamp reserves the right to modify its upgrade policy as part of its continuous efforts to improve customer service.