OpsRamp’s Release Upgrade Policy

OpsRamp’s release upgrade policy ensures timely and structured updates for all its product components, including the SaaS Platform, Agent, Gateway, Web Services Monitoring (Synthetics), and Content Releases.

The policy follows a predictable release cadence to deliver:

  • 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.

OpsRamp emphasizes compatibility, customer validation, and proactive communication:

  • Compatibility: Supports the latest three versions (N-2 policy) for Agents and Gateways.
  • Testing Opportunities: Provides non-production environments for customers to test releases in advance.
  • Notifications: Shares release schedules and updates via the System Health page, Customer Success teams, and release notes.

By separating updates for platform, agents, gateways, and integrations, OpsRamp ensures flexibility and minimal disruption to customer operations.

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.

Policy for Older Versions and Compatibility

To maintain high standards of performance and security, OpsRamp enforces a clear policy for older versions and compatibility.

Older versions are unsupported Older versions of the SaaS platform, Agent, and Gateway are not maintained or supported once a new release is deployed.Customers are encouraged to upgrade to the latest version to leverage new features and receive technical support.

Version compatibility policy OpsRamp supports the 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 are advised to review and update their custom configurations to ensure compatibility with new releases. Upgrading to the latest version ensures 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 adhering to this policy, OpsRamp ensures that customers benefit from the latest innovations while maintaining a stable and secure IT environment.

Release types and frequency

OpsRamp’s approach to release cycles and management for the SaaS product is designed to provide stability, quality and deliver new features or service enhancements and/or OpsRamp Product Components underlying such offering. OpsRamp typically follows the below three release types:

Release TypeScopeFrequencyNotification
Platform ReleasesFeature upgrades, enhancements, bug fixes, application patches.
Example: 2024.01-U1
Every 4 weeks1 week before release via Customer Success Technical Manager (CSTM) and System Health portal
Base ReleasesMajor versions to ensure compatibility with Agent and Gateway (N-2 support).
Example: 2024.01-U1
Every 12 weeks1 week before release via CSTM and System Health portal
HotfixesCritical fixes for security or platform availability.On demandPost-release notification via CSTM

Customer validation

OpsRamp provides a non-production environment for one week prior to production releases. This allows customers to test and assess any potential impact on their configurations and usage. Notifications, along with release notes, are shared in advance through customer-facing teams.

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.

Agent release

OpsRamp agents are a critical component of the platform, enabling efficient data collection, monitoring, and management of IT infrastructure. To ensure reliability, performance, and security, OpsRamp follows a quarterly release schedule for agent updates.

Agent release process

  • Quarterly Release Schedule: New agent versions are released every three months, aligned with the SaaS platform release cycle. These releases introduce new features, enhance existing capabilities, and support updates in infrastructure and integrations.

  • New Functionality: Each release focuses on delivering new features and improvements to enhance the agent’s ability to collect and process data, integrate with various environments, and support advanced monitoring requirements.

  • Critical Bug Fixes: Address known issues that could impact agent stability, performance, or security. These fixes are delivered as part of major releases or as hotfixes on demand.

The updates ensure that customers have access to the latest tools, enabling efficient and secure monitoring of their IT infrastructure while minimizing downtime and compatibility issues. Regular agent updates are essential for maintaining support and taking advantage of new functionality introduced across the OpsRamp platform.

Version compatibility

As on Sept'22, OpsRamp only supports N-2 compatibility for agent releases. Any version less than N-2 is treated as an unsupported version. Customers are requested to upgrade to the latest version of agent as available. Also, customers are expected to upgrade the agent before they submit any support request for unsupported versions.

Example: When 14.0 agent release is deployed in production, OpsRamp will provide technical support for only 12.0, 13.0 & 14.0 versions..

Release Types and Frequency

Release TypeScopeFrequencyNotification
Major ReleaseNew functionality oftentimes with major changes to the application or the architecture.Typically once every quarterTypically 3 weeks
Hot-fixHot fixes needed for system stability or securityOn Demand

Gateway release

Gateway releases are done quarterly and are an integral part of the product and provide new functionality or support enhanced architecture. Critical bug fixes and security updates are delivered as patch releases as and when needed.

Typically, Gateway release cycles are coincidental to the SaaS platform release. Updated version of OpsRamp Gateway is published to the downloads section of the portal post "Version change release" of SaaS platform.

Release TypeScopeFrequencyNotification
Major ReleasesNew functionality and architecture changes.Quarterly3 weeks before release
HotfixesCritical fixes for stability or security.On demandPost-release notification

Version Compatibility

OpsRamp supports N-2 compatibility for Gateway versions. Unsupported versions are not eligible for technical support, and customers must upgrade to the latest version.

Example: If version 14.0 is released, OpsRamp supports versions 12.0, 13.0, and 14.0.

Release Types and Frequency

Release TypeScopeFrequencyNotification
Quarterly ReleasesNew functionality and architecture changes.Quarterly3 weeks before release
HotfixesCritical fixes for stability or security.On demandPost-release notification

Web services monitoring (Synthetics)

Web services monitoring (Synthetics) is deployed in two modes:

  1. Public Collectors: Upgraded as part of platform releases.
  2. Private Collectors: Managed separately on customer gateways.

Planned changes, such as IP updates, are communicated in release notes and documentation.

Content release

Monitoring templates and integrations are classified as content updates. Since Q2 2022, content updates are separated from platform upgrades and delivered weekly. Updates are documented in the Release Notes.

Communication policy

Notification TypeDetails
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. Subscribed users receive email notifications.
Release Notes (Customer)Published on the documentation portal after the first production pod upgrade.

  1. Release Notes

  2. Deprecations

  3. Release Notes - Platform 2023

  4. Release Notes - Integrations 2023




Disclaimer

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