What's new in Virtana?
Welcome to the release notes for Virtana. The visible and not-so-visible parts of Virtana are updated regularly. This page highlights the new features and enhancements.
This month's release includes enhancements in the following products:
This month's release includes the following enhancements:
Cost meter cards are improved
These improvements make it easier for you to understand both raw and effective capacity usage so you can better track consumption, optimize resources, and plan more accurately.
You can do the following with Cost meter cards:
Meter card management: You can define meter cards granularly based on Infrastructure Observability (IO) instances and hosts.
Enhanced storage capacity visibility: The newly expanded capacity reporting provides you with a clear picture of storage utilization. Along with Actual Used Capacity and Actual Free Capacity, you can view Compressed Values, which provides visibility into post-compression savings for environments using storage efficiency features.
To learn more, see Creating Cost Meter Cards.
Topology updates
The Topology feature is updated with the following improvements:
Clustered resource view: You can now view resources in a clustered set on the Topology page, providing a more organized overview.
Expanded filters: You can now select up to 10 resources within the filter.
Entity-specific drill-down: You can now drill down into the topology of specific entities for more focused analysis.
Kubernetes resource hierarchy: You can now view Kubernetes (K8s) resources in a hierarchical structure, improving clarity and understanding of relationships.
Automated connectivity discovery: Connectivity between cloud and on-premise resources are automatically discovered, providing a more complete picture of your infrastructure.
To learn more, see Topology.
Root cause analysis in Global View
You can now better perform root cause analysis for service level objectives (SLO) alerts in Global View by showing how services are communicating with each other.
To learn more, see Causal Analysis.
Welcome to the Virtana Infrastructure Observability (IO) 2025.9.1 release!
This release includes updates to several core components, providing security enhancements and bringing them to their latest versions. These core component updates will continue for several releases.
Additionally, this month's release includes the following enhancements:
API updates
Single API for inventory data
Added a new API to provide inventory data for various compute and storage entity types, for example, All Compute Hosts, All IP Switches, and All Storage Arrays. This initial release makes available the same metrics currently displayed in Virtana IO.
Virtana IO API improvement
The Virtana IO API is now case-insensitive. Previously, the API contained upper and lower case sensitivity. This improvement now makes it easier to match on hostnames and new endpoints.
For more information, see the Public API documentation.
New metrics for Brocade Fiber Channel (FC) switches
Additional and updated metrics and properties are now in the Fiber Channel Switch Integration for Brocade FC Switches. These changes include updates for environmental details, such as temperature and fan speed.
The following metrics have been added to support Brocade FC switches. These include:
system.fan.speed: Monitors the current fan sensor reading.
brocade.san.switch.power.supply.value: Monitors the current power supply sensor reading.
system.temperature.value: Monitors the current temperature sensor reading.
For more information, see the Infrastructure Observability 2025.9.1 Metrics Guide, which you can download in the Virtana Support Portal.
New environmental metrics for Cisco Fiber Channel (FC) switches
Additional and updated metrics and properties are now in the Fiber Channel Switch Integration for Cisco FC Switches. These changes include updates for environmental details, such as sensor status, temperature, and fan speed.
The following metrics have been added to support Cisco FC switches:
cisco_entity_physical_sensor_airflow: Represents an Entity Cubic Meters per minute (airflow) Sensor value.
cisco_entity_physical_sensor_electric_current: Represents a Cisco Entity Electric Current Sensor value.
cisco_entity_physical_sensor_electric_potential_ac: Represents a Cisco Entity Electric Potential AC Sensor value.
cisco_entity_physical_sensor_electric_potential_dc: Represents a Cisco Entity Electric Potential AC Sensor value.
cisco_entity_physical_sensor_frequency: Represents a Cisco Entity Frequency Sensor value.
cisco.fru.total.availablecurrent: Total current available for FRU usage.
cisco.fru.total.drawncurrent: Total current drawn by powered-on FRUs.
cisco_entity_physical_sensor_relative_humidity: Represents a Cisco Entity Relative Humidity(RH) Sensor value.
cisco_entity_physical_sensor_rpm: Represents a Cisco Entity RPM Sensor value.
cisco_entity_physical_sensor_Rx_Tx_power: Provides the Rx_Tx power value.
cisco_entity_physical_sensor_temperature: Represents a Cisco Entity Temperature Sensor value.
For more information, see the Infrastructure Observability 2025.9.1 Metrics Guide, which you can download in the Virtana Support Portal.
New environmental metrics for Linux OS Integration
Additional metrics and properties have been added to the Linux Integration, including filesystem utilization, message queues, memory, swap, and semaphore properties and metrics.
The following metrics have been added to support Linux OS integration:
system.disk.inode.utilization
system.fan.status
system.ping.pl
system.ping.rta
system.power.status
system.temperature.status
system.voltage.status
system_linux_individual_SwapArea_Utilization
system_linux_loggedInUsers_Pct
system_linux_messageQueueIDs_Utilization
system_linux_openFileDescriptors_Utilization
system_linux_runningProcesses_Pct
system_linux_Semaphores_UsedCount
system_linux_Semaphores_Utilization
system_linux_sharedMemoryIDs_Utilization
For more information, see the Linux Operating System 3.2 Metrics Guide, which you can download in the Virtana Support Portal.
New metrics for Hitachi Content Platform
New properties and metrics have been added to the Hitachi Content Platform (HCP) Integration. These additions enhance the Node, Tenant, and Namespace areas.
The following metrics have been added to support HCP:
HCP Node
type
hardware_type
failure_status
Label
Volume
System Name
Serial Name
Compression %
version
replication_enabled
search_enabled
indexed_Volume_Capacity
shared_volume_capacity
Licensed_Capacity
HCP Tenant
Allow_search
allow-versioning
allow_replication
allowRetentionModeSelection
HCP NameSpace
Soft Quota
For more information, see the HCP 1.0 Metrics Guide, which you can download in the Virtana Support Portal.
New metrics for Hitachi NAS System Integration
Several new properties and metrics have been added to the Hitachi Network Attached Storage (NAS) System Integration. These additions focus on networking status and metrics, and include metrics for File Transfer Protocol (FTP), Common Internet File System (CIFS), Server Message Block (SMB), Network File System (NFS), Internet Small Computer System Interface (iSCSI), and ethernet.
For more information, see the Hitachi NAS 1.1Metrics Guide, which you can download in the Virtana Support Portal.
New metrics for Windows OS Integration
New properties and metrics have been added to the Windows OS Integration, including Memory, Event Log Counts, and Volume Serial Number.
For more information, see the Windows Operating System 3.1 Metrics Guide, which you can download in the Virtana Support Portal.
New SFP metrics for Cisco SAN switches
The SAN Switch Integration now support Small Form-Factor Pluggable (SFP) metric data on Cisco Storage Area Networking (SAN) switches, including light levels, power, and temperature. To collect these metrics, you must enable the NX-API interface on the switches.
For more information, see the Infrastructure Observability 2025.9.1 Metrics Guide, which you can download in the Virtana Support Portal.
New! Dell PowerProtect Integration
The new Dell PowerProtect Integration supports customers who use the Dell PowerProtect line of systems in their infrastructure. You can use this integration to help discover hardware components, construct topology views, and deliver data on the health, utilization (including capacity), and performance of these components.
This release supports properties and metrics for hardware configuration, health, utilization performance and capacity of the systems.
For more information, see the new Dell PowerProtect guides which you can download in the Virtana Support Portal.
New! Alarm engine redesigned
The redesigned Infrastructure Observability Alarm Engine is now available for testing. This updated engine can be installed and run in parallel with the current alarm system, which you can turn on using a specific property. This alarm engine focuses on Single Metric alarms that can use Properties as an evaluation source.
As a best practice, only use this updated alarm engine in lab or testing environments.
This month's release includes the following enhancements:
Amazon CloudWatch for Amazon FSx integration
The Amazon CloudWatch for Amazon FSx integration automatically discovers Amazon FSx for NetApp ONTAP instances using AWS credentials. It then ingests CloudWatch metrics into Global View, where they appear alongside existing IO-collected NetApp metrics.
Here's how it works:
Automated discovery: Cloud Gateway uses your AWS credentials to automatically find all FSx instances in your AWS environment, eliminating the need for manual setup.
Comprehensive metrics: We combine IO's in-depth NetApp expertise (ONTAP-level metrics) with CloudWatch's infrastructure metrics (cache hit ratios, AWS-specific performance data) for a complete, unified view.
Centralized alerting: FSx alerts from both sources are consolidated in Global View's alert dashboard, ensuring proper correlation and context.
Seamless integration: The solution uses your existing IO-to-Global View connectivity, requiring no changes to your current workflows.
This feature is available to existing Virtana customers with AWS FSx for NetApp ONTAP deployments who can provide AWS credentials for CloudWatch access and configure the integration using Cloud Gateway.
Google Kubernetes Engine (GKE) Autopilot cluster support
Virtana is now recognized as a Google Autopilot partner, so you can deploy Virtana Container Observability on Google Kubernetes Engine (GKE) Autopilot clusters. This deployment provides comprehensive visibility into dynamic, containerized workloads running on GKE Autopilot.
For more information, see Deploy Virtana CO South on GKE Autopilot clusters.
Improved download support
You can now export your Kubernetes data to a PDF or CSV file. Previously, you could only export the data that was displayed in the window.
This month's release includes the following enhancements:
Virtana Web Analytics
Admins can now access a unified dashboard that delivers deeper insights into how teams are using the Virtana Platform, including Container Observability. This dashboard tracks user logins, time spent within the platform, and the most frequently accessed features, so decision-makers can assess adoption and measure return on investment.