Release Notes

This release marks general availability (GA) of the new alarms engine for Virtana Infrastructure Observability (IO), replacing the previous alarm engine. Built over the past year, the new engine delivers improved performance and adds capabilities that weren't previously available, and it serves as the foundation for future Virtana AI Observability Platform alarming capabilities.

The new engine adds the following capabilities:

Existing alarm rule templates, including single-metric alarms and other use-case-specific templates, are migrating to the new engine. Starting with this release, all existing alarm rule templates run through the new engine by default.

This release also adds proxy server support for the Actions Engine.

For more information, see Alarms and Cases

The Balance Finder Analytic adds support for Cisco STS FCP metrics, ProbeSW Fibre Channel over Ethernet (FCoE) metrics, and Unified Computing System (UCS) host bus adapter (HBA) metrics in balance calculations. Entity traversal also supports additional host types as a starting entity. As a result, you can include a wider range of storage and compute metrics when you calculate balance.

For more information, see Balance Finder.

VM Coordinator supports all Nutanix Acropolis Hypervisor (AHV) virtual machines (VMs) and hosts, and VM Deployment Advisor supports Nutanix AHV. Capacity Forecaster supports additional Hyper-V metrics. As a result, you get deployment and capacity guidance across more of your virtualized environment.

The Nutanix integration supports Volume Groups and their associated metrics, and Smart Groups and their associated properties. As a result, you can monitor and group Nutanix storage resources with more granularity.

For more information, see Integration User guide

The Hyper-V integration supports System Center Virtual Machine Manager (SCVMM) as a discovery source, in addition to the existing server-defined integration functionality. SCVMM discovery also automates subscription and unsubscription of discovered Hyper-V servers. The public application programming interface (API) supports create, read, update, and delete (CRUD) operations for the Hyper-V integration. As a result, you can discover Hyper-V servers automatically and manage the integration programmatically.

For more information, see Integration User guide

The Dell PowerMax integration uses the Unisphere Enhanced API to run bulk queries against the Unisphere metrics database. This release also adds metrics for front-end ports and storage groups for internal and external timing, and collects environmental metrics at the array level. As a result, you get broader and more efficient metric collection from PowerMax arrays.

For more information, see Integration User guide

Two new integrations are generally available (GA) in this release. The Dell ObjectScale integration supports the Dell ObjectScale platform at the appliance and object storage levels. The Compute Redfish integration uses the Redfish Distributed Management Task Force (DMTF) standard to collect compute hardware data through embedded controllers or the Intelligent Platform Management Interface (IPMI). As a result, you can monitor Dell ObjectScale storage and Redfish-compliant compute hardware, including inventory, health status, and environmental metrics.

For more information, see Integration User guide

The UI settings dialog supports custom image and branding uploads. As a result, you can apply your own logo and images across all displayed pages.

Reports and charts for all chart types support percentile values, and alarm rules can use those percentile values as a condition. As a result, you can build alarms and visualizations based on percentile thresholds instead of only averages or raw values.

The Network Utilities and Health areas add a log viewer, Network Time Protocol (NTP) server status reporting, a netcat (nc) utility, and disk space usage reporting. The log viewer monitors service logs on the appliance in real time and lets you copy or download logs for offline review. The NTP report shows the status of configured NTP servers. The netcat utility tests whether a given IP address and listening port are reachable over the network. The disk space report shows appliance disk usage (equivalent to df -h). As a result, you can diagnose appliance, network, and time-synchronization issues directly from the UI.

For more information, see Network and Utilities

Using OpenTelemetry (OTEL) to push data from the public API to a defined receiver is generally available (GA) in this release. As a result, you can export IO metrics to your OTEL-compatible observability pipeline.

Several IO core components are updated in this release to apply security fixes and bring them to their latest available versions. Virtana continues these core component updates over several release cycles.

For more information, see the IO release notes.

The core OS upgrade is generally available (GA) in this release. You install the upgrade in place, using the same update bundle (UPD) process as a standard IO update. Starting with this release, every update bundle includes and applies the OS upgrade by default. The OS upgrade is optional in this release. Virtana recommends applying it as soon as possible. As a result, new update bundles keep the underlying operating system current automatically.

Starting with this release, a firmware update is available for ProbeFC-16 and ProbeFC-32 performance probes. The firmware updates the probe OS to openSUSE 16.0 and applies security updates. As a result, your ProbeFC probes receive the same OS and security baseline as the IO appliances.

You upload the firmware update to the portal, then push it to the probes, the same way as previous updates. The OS upgrade is an in-place upgrade, similar to the IO appliance upgrade. Depending on the firmware version running on your probes, you might need more than one upgrade cycle. For more information, see the firmware release notes.

Backups taken from 2026.6.1 or earlier cannot fully restore Neo4j entity data on 2026.9.1 due to Neo4j database upgrade changes. Although the restore may complete successfully, metrics and inventory data may be incomplete. Configuration data is restored successfully.