Common Gateway Enhancements

Support for OpsRamp Gateways on HPE VME

You can install Classic and NextGen Gateways on HPE VME as the hypervisor layer. This is supported for Gateway versions 20.0.0 and 21.0.0, using both ISO and OVA images for each gateway type.
Refer to the following documents for more details:
Install NextGen Gateway on HPE VME using ISO
Install NextGen Gateway on HPE VME using OVA
Install Classic Gateway on HPE VME using ISO
Install Classic Gateway on HPE VME using OVA

Audit Logging Enabled for Gateways

Audit logging support is now enabled for both Classic and NextGen Gateways. The auditd package, minimal audit rules, and log rotation configuration are included by default in ISO/OVA installations and are also available through patches for existing deployments.
Refer to the following documents for more details:
Audit Logging Configuration for NextGen Gateway
Audit Logging Configuration for Classic Gateway

Database Optimization

As part of ongoing performance and maintenance improvements, we have optimized the PostgreSQL database by removing redundant indexes for important tables. The identified unused indexes were dropped to reduce storage overhead, free up database space, and improve overall query performance and efficiency.
This change does not impact application functionality and is part of routine database optimization efforts.

Purging Expired Gateway Data

OpsRamp Gateway 21.0.0 automatically purges expired monitoring and alert data accumulated during prolonged tunnel disconnects, in accordance with OpsRamp retention policies.
This prevents unnecessary data processing after tunnel reconnection and reduces load on the gateway and backend database.

Vprobe logs Enhancement

OpsRamp Gateway 21.0.0 updates the log severity for gateway monitoring messages in vprobe logs. Informational messages related to repository status and connection health are now logged at the INFO level instead of ERROR.
This change prevents normal gateway behavior from being misclassified as an error, reducing false alarms and improving log clarity for operators and support teams.

Common Gateway Security Fixes

Firefox Browser Upgrade

We have identified and addressed compatibility requirements by upgrading the Firefox browser used by Webprobe application to Mozilla Firefox 147.0.3 for Gateway version 21.0.0.
This update ensures compatibility with the latest synthetics monitoring capabilities and aligns the Webprobe image with current browser standards.

Known Vulnerability in Google Chrome Package

We have identified and addressed multiple security vulnerabilities in the Google Chrome browser used by the Classic and NextGen Gateway.
This update includes an upgrade to Google Chrome version 145.0.7632.75 for Linux, mitigating high‑severity issues, including an actively exploited vulnerability, and improving overall gateway security.

  • If you are planning to upgrade to version 21.0.0, no action is required. The patch will automatically update the package.
  • If you are not upgrading to 21.0.0, you must manually update the package using one of the following methods:

OpenSSL Version Update

We have identified and addressed security vulnerabilities by updating the OpenSSL package in the Gateway 21.0.0 release. The gateway now ships with OpenSSL version 3.0.2‑0ubuntu1.21, which includes the latest security fixes available from the supported Ubuntu package stream.
If you are not upgrading to version 21.0.0, you can still upgrade later to receive this update and benefit from improved security.

Classic Gateway Security Fixes

Django Package Update

We have identified and addressed known vulnerabilities in the Django package used by the OpsRamp Gateway.
This update mitigates a denial‑of‑service risk related to HTML processing and improves overall gateway security and stability.

  • If you are planning to upgrade to version 21.0.0, no action is required. The patch will automatically update the package.
  • If you are not upgrading to 21.0.0, you must manually update the package using the following method:

Classic Gateway Bug fixes

Improved Handling of Orphaned SerialUI Processes

OpsRamp Gateway includes enhanced handling for orphaned SerialUI processes to prevent excessive log growth and disk space exhaustion.
This improvement automatically cleans up inactive SerialUI processes and manages the size of the associated log file, reducing the risk of the gateway filesystem entering Read‑Only mode and improving overall gateway stability.
Refer to the Handling Orphaned SerialUI Processes and Read‑Only Mode document for more details.

NextGen Gateway Enhancements

K3s Audit Logging Enabled for NextGen Gateway

Audit logging support is now available for NextGen Gateway Kubernetes (K3s) cluster‑level changes.
This enhancement records key activities such as configuration updates, workload changes, and access control modifications, improving traceability for troubleshooting and security compliance.
Refer to the Enable K3s Audit Logging for NextGen Gateway document for more details.

NextGen Gateway Security Fixes

PostgreSQL Upgrade

In NextGen Gateway 21.0.0, the embedded PostgreSQL database has been upgraded to a supported version.
This update removes dependency on an End‑of‑Life PostgreSQL release used in earlier gateway versions and improves long‑term supportability and security.

Classic Apps Enhancements

VMware Resource Hierarchy Now Available as Labels

OpsRamp included VMware parent hierarchy details as custom attributes for all VMware resources. These attributes are also exposed as metric labels, so you can filter more accurately and build dashboards more easily.
Attribute mappings by resource type:

  • Datacenter: vCenter IP Address, vCenter Name
  • Cluster: vCenter IP Address, vCenter Name, Datacenter Name
  • Host (within a cluster): vCenter IP Address, vCenter Name, Datacenter Name, Cluster Name
  • Host (standalone): vCenter IP Address, vCenter Name, Datacenter Name
  • Virtual Machine (on a clustered host): vCenter IP Address, vCenter Name, Datacenter Name, Cluster Name, Host Name, Host IP Address
  • Virtual Machine (on a standalone host): vCenter IP Address, vCenter Name, Datacenter Name, Host Name, Host IP Address
  • Datastore: vCenter IP Address, vCenter Name, Datacenter Name, Host Name, Host IP Address, Cluster Name
  • Datastore (on a standalone host): Host Name, Host IP Address

FortiGate Native Backup/Restore Improvements

OpsRamp implemented a new backup method for FortiGate firewall configurations to improve restoration reliability. When available, backups will now be captured using the sys_config system file over SCP. If SCP access is not supported, the system will automatically fall back to the previous method using the show full-configuration or show commands over the SSH console.

VMware VM Hardware Details Collected During Discovery

OpsRamp VMware discovery now captures the new custom attribute VM Total Disk Capacity and populates it for VMware virtual machines.

Collect Device SNMP Walk via UI

OpsRamp has introduced UI-based support for performing a complete SNMP walk on devices.
This enhancement allows you to retrieve all device-supported OIDs directly from the UI without manually executing SNMP walk commands from the gateway CLI.

vCenter TLS Certificate Expiry Monitoring via REST

OpsRamp supports monitoring the TLS certificate expiry of VMware vCenter Appliance directly over HTTPS using vCenter REST APIs. This approach does not require shell or bash access to the vCenter Appliance.

Classic Apps Bug Fixes

F5 Startup Config Runs Only When You Select It

For F5 devices, OpsRamp Gateway attempts startup configuration (startup-config) backup only when you explicitly select it in the Network Configuration Backup job.

Previously, the gateway could attempt startup-config collection even after you removed (unselected) Startup Config from the job, which could cause unnecessary backup attempts and related alert noise. With this fix, backup behavior matches the job options you choose.

  • If Startup Config is selected: the gateway attempts startup-config backup for F5 devices.
  • If Startup Config is not selected (or removed): the gateway does not attempt startup-config backup for F5 devices.

Fix for Monitor Policy Creation with “In List/Not in List” Operators

OpsRamp resolved an issue where monitoring could fail if String in List or String Not in List conditions were configured with only a single value. This defect could prevent monitoring data collection.
With this fix, single‑value list configurations now work as expected.

SNMP Hexadecimal Conversion Fix for Metrics and Monitors

OpsRamp added fixes to support converting different hexadecimal formats received from end devices into multiple human-readable data formats in SNMP monitoring.

Hexadecimal → Decimal (numeric)
Supported examples:

  • 1A → 26
  • FF → 255
  • 0x1A / 0X1A → 26
  • 0A:1B:2C:3D / 0A-1B-2C-3D / 0A 1B 2C 3D → 169552957
  • 0x0A:1B:2C → 658220

Hexadecimal → String (ASCII)
Supported examples:

  • 48:65:6C:6C:6F / 48 65 6C:6C:6F / 48-65-6C:6C:6F / 0x48:65:6C:6C:6F / 48656C6C6F → Hello
  • 54:68:65:20:51:75:69:63:6B → The Quick
  • 57 6F 72 6C 64 → World
  • 30 → 0

Hexadecimal → IP
Supported examples:

  • C0:A8:01:01 / C0 A8 01 01 / C0-A8-01-01 → 192.168.1.1
  • 0x0A:00:00:01 → 10.0.0.1

Reliability Fixes for SNMP Agentless Monitoring

OpsRamp added a fix for RSE monitoring failing on Windows devices when scripts included the custom.script.multi.arguments parameter.

SNMP Trap Exclude Configuration Loading Fails During Gateway Upgrade

OpsRamp fixed an issue where the SNMP trap exclude configuration failed to load during a gateway upgrade due to a failure in the initial database read attempt.
The system now includes retry support to ensure the configuration loads successfully even when the first attempt encounters a transient failure. This improvement prevents trap-processing issues caused by incomplete configuration loading.

SNMP Extended Monitoring Template Application Fix

OpsRamp fixed an issue where applying or updating an SNMP Extended Monitoring template during active polling could disrupt running monitoring jobs.
You can apply the same template to multiple devices during polling without impacting ongoing SNMP Extended Monitoring.

Improved vCenter Hostname and URL in VMware Alerts

OpsRamp resolved an issue where VMware alerts occasionally displayed incorrect or inconsistent vCenter hostname and URL details. vCenter information in VMware alerts will now appear accurately and consistently.