check-circle-line exclamation-circle-line close-line

VMware vRealize Operations Manager 8.0 |  2019 | Build 14857692

VMware vRealize Operations Manager Upgrade Pack from 6.6.1, 6.7, and 7.x to 8.0  |  2019 | Build 14857694

Note: In this release, there is a single upgrade .pak file which includes the OS and vApp upgrade files.

VMware vRealize Operations Manager 8.0 Endpoint Operations Agents |  2019 | Build 14827011

VMware vRealize Operations Manager 8.0 Endpoint Operations Agents PAK Updates |  2019 | Build 14827024

VMware vRealize Operations Manager 8.0 Pre-Upgrade Assessment Tool |  2019 | Build 14876945

VMware vRealize Application Remote Collector 8.0 |  2019 | Build 14660115

Check frequently for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

Product Enhancements

The vRealize Operations Manager 8.0 release focuses on ease of use, faster time to value, an integrated cloud management platform, and extensibility to your environment through new and enhanced integrations. Within the existing tenets of performance, capacity, configuration, and compliance, this release brings in new features such as the cloud management platform, troubleshooting workbench, native service discovery, and application-aware infrastructure monitoring, which helps you manage your multi-cloud environments, hosting both traditional and modern applications.

Here are the key features and capabilities:

Continuous Performance Optimization

  • Fully automated workload balancing across clusters based on business intent and operational intent for workloads running on a VMware Cloud on AWS environment.
  • Integration with vRealize Automation 8.0 for initial and ongoing workload placement.

Efficient Capacity and Cost Management                                  

  • Capacity Management Enhancements
    • Ability to set capacity buffers for cluster and datastore cluster objects.
  • Capacity Monitoring Enhancements
    • Ability to monitor VMware Cloud on AWS costs using bills from the VMware Cloud Service portal.
    • Ability to combine private, hybrid, and public cloud costs in dashboards and reports.
    • Ability to track outstanding and year-to-date costs.
    • Breakdown of cost:
      • By subscriptions
      • On-Demand
      • By purchase history
  • Capacity Planning Enhancements
    • HCI capacity/cost management and planning. This release supports the infrastructure that runs vSAN software. 
    • Enhanced private cloud-costing with per datacenter cost drivers:
      • Ability to specify costs per datacenter.
      • Enhanced network cost driver support for 25, 40, and 100 GB NICs.
      • Depreciation metrics for hosts.
    • Private cloud cost comparison across data centers for new workload planning:
      • Ability to compare VM costs across multiple datacenters.
      • Ability to select existing VMs or enter a profile for new VMs.
      • Ability to identify the cheapest cluster to run the workload.
      • Ability to link to the Add Workload scenario to quantify capacity shortfall.

Simplified Troubleshooting and Intelligent Remediation

  • Application Operations
    • Enhanced ability to monitor applications using Telegraf agents. Support for twenty applications and the most commonly used operating systems. Added support for applications such as NTPD, Java, and WebSphere.
    • Ability to download Telegraf agents on Windows machines without the need to disable User Account Control (UAC).
    • Support for additional metrics, KPIs, and out-of-the-box alerts for all the supported applications.
    • Ability to view CPU, memory, and disk utilization of the top-10 processes running on a virtual machine.
    • Agent-less discovery of software processes and services running on a virtual machine.
    • Ability to intelligently build business application relationships based on discovered services.
    • Ability to troubleshoot guest operating systems and application-related issues using custom script execution.
  • Enhanced Alerting Capabilities
    • ​Improved alert detail page with a simplified workflow to act on an incident.
    • Alert analysis with the Related Alerts tab using smart grouping to do recurrence analysis, peer impact, and relational impact.
    • Capability to automatically generate potential evidence leading to a root cause, with a quick launch into the Troubleshooting Workbench.
  • Accelerated Root Cause Analysis using the Troubleshooting Workbench
    • A unique troubleshooting tool that leverages machine learning algorithms to provide relevant pieces of evidence to arrive at a potential root cause.
    • Leverages relationship topology and time scope to automatically create impact scope to gather evidence.
    • Ability to set up a custom scope and to dynamically add peers to a topology to gather evidence from the peers. For example, all the VMs under the same application tier.
    • Ability to expedite troubleshooting by intelligently gathering and correlating information around:
      • Events - Includes metrics which have breached the usual behavior and major events which have triggered, within the selected scope and time.
      • Property changes - Includes impactful configuration changes which were discovered, within the selected scope and time.
      • Anomalous metrics - Includes a ranked set of metrics which have shown patterns of drastic change, within the selected scope and time.
    • Ability to easily identify potential evidence for further analysis to arrive at a root cause.
    • Ability to run multiple troubleshooting workbenches to deal with multiple incidents.
    • Availability of multiple points to launch into the troubleshooting workbench for easy and contextual access. For example, from the Object Summary page, Alert details, and Workbench under the Home page.

SDDC Configuration and Compliance

  • Enhanced and simplified workflows for compliance management. Grouping of benchmarks for easy navigation and better visual representation.
  • New enhancements to regulatory and SDDC (vSphere, NSX, and vSAN) compliance content.
  • Ability to monitor compliance for VMs managed by you in VMware Cloud on AWS.
  • Ability to import and export custom compliance standards.
  • Auto-remediation of compliance configuration drifts using the vRealize Orchestrator Management Pack.

Cloud Management Platform

  • Tighter integration between vRealize Operations Manager and vRealize Automation offers benefits of a single cloud management platform.
  • Ability to share common constructs such as cloud accounts, cloud zones, and projects across vRealize Operations Manager and vRealize Automation.
  • Ability to understand deployment cost:
    • Evaluate upfront costs on vRealize Automation.
    • Monitor ongoing costs per VM, deployment, or project.

Platform Enhancements

  • AWS and Microsoft Azure public cloud monitoring:
    • Ability to manage AWS and Microsoft Azure deployments natively.
    • Ability to discover and monitor inventory and services across multiple regions and accounts.
    • Built-in dashboards and predefined alerts to simplify troubleshooting.
  • Continuous availability:
    • Capability to extend vRealize Operations Manager cluster nodes across multiple availability domains.
    • Ability of the cluster to resist up to one availability domain failure and to recover without causing any downtime.
  • Runs on a new, more secure, and advanced operating system.
  • Simpler workflows for management and configuration of cloud accounts and other integration accounts.
  • REST API enhancements:
    • New REST API for setting the currency.
    • Support for a secure token-based authentication for API access.
  • Simpler initial onboarding with guided tours.
  • Enhanced Solutions Repository page for easier navigation.
  • Upgrade simplification by using a single .pak file to upgrade to vRealize Operations Manager 8.0.

Dashboards, Widgets, Reports, and Views Enhancements

  • Ability to re-run reports from the Generated Reports tab.
  • Modern layout and menus for the Manage Dashboard, Views, and Reports pages.
  • Support for the color picker for pie-charts in views.
  • Support for the doughnut type pie-chart in the distribution view.

Root and Admin Password during Upgrade

During upgrade, the vRealize Operations Manager 8.0 Pre-Upgrade Assessment tool checks for a locked or expired password for the admin account or an auto-generated password for the root account. If a fault is found, the upgrade fails. For more information see KB 75195.

Date Format Change

Depending on the browser language you choose, dates are displayed in the respective language format. For example, if you set the browser language to en-GB, dates are displayed in the dd/mm/yy format.

Geode Version

The Geode version has been upgraded to version 1.7 in this release. 

Workload Utilization Widget

The Workload Utilization widget has been discontinued starting from this release. In future releases, the widget will not exist, and it is recommended that you update your dashboards accordingly. 

End Point Operations Management Agent

The End Point Operations Management agent functionality has been replaced with the Telegraf agent. The current release is the last release of vRealize Operations Manager in which the End Point Operations Management agent is available. 

VMware Cloud on AWS SDDC

To ensure compliance of your workload on VMware Cloud on AWS, vRealize Operations Manager 8.0 includes compliance alerts for customer managed VMs. 

Basic Authentication

Basic authentication using the REST API is deprecated and disabled in vRealize Operations Manager 8.0 by default. Use token-based authentication instead. 

Metrics and Properties Enhancements

The following KB article describes all the metrics and properties that have been added in vRealize Operations Manager 8.0:

Metrics added in vRealize Operations Manager 8.0 (74950)

New and Updated Management Packs and Compliance Packs: 

  • The VMware Management Packs and Compliance Packs that are new and those that are updated with significant changes for vRealize Operations Manager 8.0 are:
    • VMware vRealize Operations Management Pack for CloudHealth 1.0
    • VMware vRealize Operations Management Pack for vRealize Orchestrator 3.1
    • VMware vRealize Operations Management Pack for NSX-T 2.2
    • vRealize Operations Management Pack for Storage Devices 8.0
    • vRealize Operations Compliance Pack for DISA 1.0.1

Refer to the VMware Product Interoperability Matrix for all VMware Management Packs supported with vRealize Operations Manager 8.0.
The 3rd party authored Management Packs that are supported with 8.0 are listed in the VMware Compatibility Guide.


System Requirements

Review this section before you install or update vRealize Operations Manager.

Sizing and Scaling

The CPU, memory, and disk requirements that meet the needs of a particular environment depend on the number and type of objects in your environment and data collected. This includes the number and type of adapters installed, the use of HA (High Availability) and CA (Continuous Availability), the duration of data retention, and the quantity of specific data points of interest. VMware updates Knowledge Base article 2093783 with the most current information about sizing and scaling. The Knowledge Base article includes overall maximums and spreadsheet calculations that provide a recommendation based on the number of objects and metrics you expect to monitor.

Deployment Formats

You can deploy vRealize Operations Manager 8.0 with VMware virtual appliance.

If you are deploying a vRealize Operations Manager virtual appliance, use a VMware vSphere Client to connect to a VMware vCenter Server, and deploy the virtual appliance through the vCenter Server instance. The vRealize Operations Manager virtual appliance must be deployed on hosts that are:

  • ESX/ESXi 6.0 or later (with the exception of ESX/ESXi 6.5 that must be with a patch not lower than ESX/ESXi 6.5 Update 1) and managed by VMware vCenter Server 6.0 or later. 
    • ESX/ESXi 6.5 with build number lower than 5969303 must be updated to a higher patch.
  • If you have vRealize Operations Manager virtual appliance deployed on ESXi 5.5 hosts, you must first upgrade the vCenter Server to versions 6.0 or 6.5, and then upgrade to vRealize Operations Manager 8.0.

Applying License Keys

IMPORTANT: A new license key is required for upgrading vRealize Operations Manager 7.0 and later versions. All license keys except vRealize Operations for Horizon, vSOM Enterprise Plus and its add-ons are invalidated. The product will work in evaluation mode until a new valid license key, which can be obtained from the MyVMware portal, is installed. After you log in to the user interface of vRealize Operations Manager, if you see that you are using an evaluation license, consider applying for a new license before the end of the 60-day evaluation period. 

For more details on entitlements of vRealize Operations editions, see the edition comparison table from the following link:

SDDC Compliance 

To ensure compliance of your vSphere, VMware Cloud on AWS,  and vSAN 6.7, 6.5, and 6.0 objects, and also NSX-T 2.3, 2.4, and 2.5, and NSX-V 6.3.x and 6.4.x objects, vRealize Operations Manager 8.0 includes compliance alerts for VMware vSphere Security Configuration Guide versions 6.7 Update 1, 6.5, and 6.0. These security configuration guide alerts are based on the corresponding object types. Some of the alerts and symptoms are available only for backward compatibility with older versions of vSphere, even though the current release supports the latest vSphere Security Configuration Guide 6.7 Update 1. 

Solutions Support

In addition to the VMware solutions (vSphere, Endpoint Operations Management, and vRealize Log Insight), see the Solution Exchange marketplace for many more solutions. These solutions work with Virtual Appliance single or multiple nodes.

TLS Support

When you upgrade your vRealize Operations Manager instance to 8.0, both TLS 1.0 and TLS 1.1 are disabled on all the vRealize Operations Manager nodes. TLS 1.2 is the only protocol that will be supported by default. However, if you want to lower the security bar and enable TLS 1.0 and 1.1, you can still do so, see KB 74951 for more information. TLS 1.0 and TLS 1.1 settings are preserved during upgrade.

VMware Product Compatibility

Note: The VMware Product Interoperability Matrix provides details about the compatibility of vRealize Operations Manager with VMware products.

Browser Support

This vRealize Operations Manager release supports all current Web browsers, although only the following browsers were tested with this release:

  • Google Chrome: Version 76 and 77
  • Mozilla Firefox: Version 68 and 69 
  • Microsoft Internet Explorer: Version 11 (limited support)
  • Microsoft Edge 17 and 18
  • Safari 12 and 13

Installing and Upgrading vRealize Operations Manager

Note: While upgrading to vRealize Operations Manager 8.0, the expected size of the root partition for Photon OS is 20 GB. For information about this requirement, see KB 75298.

Note: Reapplication of the vRealize Operations Manager 8.0 upgrade .pak file over an existing vRealize Operations Manager 8.0 version is not supported and will result in a failure.

Unless upgrading from vRealize Operations Manager 6.7 or above, it is imperative that you run the Pre-Upgrade Assessment tool. A pre-upgrade assessment report that is generated will provide you with the recommended replacements. This tool provides you with an impact analysis following the reduction of metrics in various versions of the product. For more details on using the Pre-Upgrade Assessment Tool, see KB 74952. It is always recommended to run the Pre-Upgrade Assessment tool before an upgrade.

Refer to the vRealize Operations Upgrade Center that has information about upgrading vRealize Operations. Refer to the VMware Lifecycle Product Matrix for information about supported versions of vRealize Operations Manager.

After upgrading, it is necessary to update Endpoint Operations agents. For more information, see KB 2137709 and KB 2138748.

The vRealize Operations Manager Information Center has detailed information about installation and software updates.

Refer to the vRealize Operations Manager vApp Deployment and Configuration Guide that provides guidance for a vRealize Operations Manager virtual appliance, before you install or update vRealize Operations Manager.

Upgrading to vRealize Operations Manager 8.0, resets out-of-the-box content as part of the software upgrade process even if the Reset Default Content button is unchecked during the upgrade. This implies that the user modifications made to default content such as alert definitions, symptom definitions, recommendations, policies, views, dashboards, widgets, and reports are overwritten. You need to clone or backup the content before you upgrade to vRealize Operations Manager 8.0.

Deploy vSphere with Operations Management (any edition) and vRealize Operations Standard together in one deployment.

Deploy vCloud Suite/vRealize Suite Standard, Advanced, or Enterprise and vRealize Operations Advanced or Enterprise edition together in one deployment.

Note: You can also install vRealize Operations Manager by using vRealize Suite Lifecycle Manager. For more information, see Creating an Environment. To automate installation, configuration, upgrade, patch, configuration management, drift remediation and health from within a single pane of glass, you can use vRealize Suite Lifecycle Manager. If you are a new user, click here to install vRealize Suite Lifecycle Manager. This provides IT managers or cloud admin resources to focus on business-critical initiatives, while improving time to value (TTV), reliability, and consistency.

See the Installation and Upgrade Issues section for issues related to installing vRealize Operations Manager or updating the software.

Resolved Issues

  • The compliance score differs on different analytics nodes in vRealize Operations Manager

    The user interface of different analytic nodes shows different scores for Compliance for all seven compliance policies. For more information, see KB 70665.


  • The state of a service in a non-existing state remains as is even when it starts collecting data

    If you edit the configuration of a service in a non-existing state, the service remains in a non-existing state even when it starts collecting data.


  • Advanced filtering conditions are ignored in the Environment Status widget

    In the Environment Status widget, the advanced filtering conditions are ignored if an option is selected in the tag filter.


  • Inconsistent tag violations in the Workload Optimization page

    When there is more than one tag assigned to a cluster and cluster-based intent is enabled, there is an inconsistent tag violation in the Workload Optimization page.


  • The Logs tab displays a message that states that vRealize Operation Manager is not integrated with Log Insight

    If the VMware vRealize Log Insight Management Pack has not been activated from the Administration > Solutions > Repository page, the Logs tab displays a message.


  • Application services are in a stopped state when you start an agent during application monitoring

    The application services activated in vRealize Operations Manager 7.0 are in a stopped state after you stop and then start an agent. This occurs when vRealize Operations Manager is upgraded to 7.5 and vRealize Application Remote Collector is upgraded to 7.5.


  • After you upgrade from VMware Application Proxy 1.1 to vRealize Application Remote Collector 7.5, services are not discovered

    After you upgrade from VMware Application Proxy 1.1 to vRealize Application Remote Collector 7.5, even if the application services are running, vRealize Application Remote Collector does not discover them. 


  • Agent Installation on Windows Server 2012 fails

    You cannot install agents on Windows Server 2012 if you have Visual C++ older than version 14. 


  • Objects such as images and icons related to the Management Pack for vRealize Orchestrator are not displayed 

    After you upgrade vRealize Operations Manager, if you scale a vRealize Operations Manager cluster with the Management Pack for vRealize Orchestrator 2.0 installed and add another vRealize Operations node, some objects such as images and icons related to the Management Pack for vRealize Orchestrator 2.0 are missing.


  • VVOL datastores are masked

    If a VM, host, cluster, datacenter, or vCenter Server object with VVOL datastores is selected, an incorrect datastore count appears on the Environment Objects Map or the Troubleshooting All Metrics page. And if a VM is deployed on a VVOL datastore, raw or derived metrics may be missing.


Known Issues

The known issues are grouped as follows.

Installation and Upgrade Issues
  • The rsyslog service does not run with vRealize Operations Manager parameters

    For vRealize Operations Manager 8.0 setups that are freshly deployed, the rsyslog service does not release old files. This causes the / partition to fill up.

    Workaround: Restart the rsyslog service on all nodes or restart vRealize Operations Manager VMs. For more information, see KB 76154.

  • Batch installation ignores the custom certificate

    During a multi-node cluster deployment, the deployment wizard ignores the custom certificate even if it is provided and uses the default certificate.

    Workaround: None

  • The Take Node(s) Offline wizard appears when you try to bring an offline RC node online

    When you try to bring an RC node back online after having just taken it offline, the Take Node(s) Offline wizard appears when you click the Take Node Offline/Online button, instead of the Take Node(s) Online wizard as expected.

    Workaround: If the node state still displays as Running or the status is still Online after having taken it offline, wait a few moments and then manually refresh the data in the view from the top menu to get the latest state of the node. After the correct state is displayed which is Not Running, the Take Node Offline/Online button will work as expected.

  • Node replacement fails while replacing all nodes in the fault domain

    If the nodes that are replaced are not powered off, it might result in an unusable state of the cluster.

    Workaround: While replacing nodes in a CA enabled cluster, ensure that the nodes are powered off.

  • Nodes are marked as Configured instead of New

    When the Multiple Nodes Addition wizard detects that a wrong admin password is provided, node addition is canceled, but new nodes are marked as Configured.

    Workaround: Redeploy the nodes and restart with a correct admin password.

  • Even if the cluster state is set to Failure, the cluster is functional

    The state of the cluster is incorrectly set to Failure if you use the Bring Online button from the witness node.

    Workaround: Do not use the witness node to bring the cluster online.

  • Installation of a management pack fails on a newly added node

    After you upgrade to vRealize Operations Manager 8.0, installation of a management pack fails on a newly added node.

    Workaround: Upgrade management packs to their latest version and then add a new node.

  • Upgrade to vRealize Operations Manager 8.0 fails for instances with Wavefront configuration

    If you use vRealize Operations Manager 7.5 and earlier versions with Wavefront configured, you cannot upgrade to vRealize Operations Manager 8.0 as upgrade fails.

    Workaround: None

  • In a pure IPv6 environment, DNS servers are missing from the /etc/resolv.conf file

    DNS servers are missing from the /etc/resolv.conf file when a new node is deployed in a pure IPv6 environment. As a result, the node cannot resolve FQDNs to IP addresses.

    Workaround: With the help of your network administrator, manually set the DNS servers in the /etc/resolv.conf file.

  • Upgrade might fail if any of the nodes are running on VMs with US/Pacific-New timezone

    PostgreSQL database systems no longer support the US/Pacific-New timezone, which was just an alias for America/Los_Angeles timezone. If any of the vRealize Operations Manager nodes are running on VMs with US/Pacific-New timezone, upgrade might fail.

    Workaround: Change VM timezones from US/Pacific-New to America/Los_Angeles, and then upgrade.

General Issues
  • While monitoring applications, you cannot activate a plugin with the same fields till the plugin configuration is deleted

    An error message is displayed in the user interface of vRealize Operations Manager that states the following: 'Failed to update resource: Resource with same key already exists'.

    Workaround: Manually delete the existing plugin configuration and then continue with the activation of the plugin. If the problem persists, delete the corresponding resource from the inventory.

  • The compliance score for a user with limited object visibility is the same as for a user with complete object visibility

    The compliance score is calculated for objects that are not visible (not assigned) to the current user.

    Workaround: Complete the following steps:

    1. Create a custom group with objects visible (assigned) to the user.
    2. For that group, apply a policy in which the needed set of compliance alert definitions is enabled.
      If that set is enabled only in one active policy (the one that is applied to the custom group), the compliance benchmark based on those alert definitions will display the correct score.


  • Historical data is not displayed for application plugins if the vCenter PNID is modified

    The historical data or data prior to changing the vCenter PNID is lost for the application plugins.

    Workaround: None

  • SharePoint service is not discovered with Service Discovery

    Since IIS and SharePoint services have common ports, IIS takes the ports from SharePoint and the SharePoint service is not discovered with service discovery.

    Workaround: None

  • The status of a few plugins is Unknown after vRealize Application Remote Collector and vRealize Operations Manager is upgraded from 7.5 to 8.0

    When you upgrade vRealize Application Remote Collector and vRealize Operations Manager from 7.5 to 8.0, the Unknown icon is displayed along with a gray icon. 

    Workaround: Reactivate the plugin.

  • Upgrade from vRealize Operations Manager 7.5 to 8.0 results in a change in the license cost driver

    When you upgrade from vRealize Operations Manager 7.5 to 8.0, there is a change in the license cost driver between the Summary page and the License Cost Driver page.

    Workaround: You can set the cost with the old value, which is $365, in the License Cost Driver page.

  • Execute Script and Get Top Processes actions do not work from the Inventory > Objects page

    After Service Discovery is configured and you navigate to the Inventory > Objects page, select any VM for which Service Discovery is in the Collecting state with a Data Receiving status. Run the Execute Script and Get Top Processes actions for the VM. Incorrect windows are displayed.

    Workaround: If a VM is selected from the Inventory > Objects page, click Show Detail from the toolbar. You will see the VM's Summary page from where you can run the Execute Script and Get Top Processes actions.

  • vRealize Automation 8.x stops collecting data
    1. If vRealize Automation 8.x services have stopped, data is not collected. 
    2. When vRealize Automation 8.x services are running, data is not collected intermittently.


    1. Start vRealize Automation 8.x services and ensure that all the vRealize Automation 8.x services are running. Wait for about 20 mins.
    2. Restart the vRealize Automation 8.x adapter instance.
  • While installing an application monitoring agent using an Internet Explorer browser, a message is displayed asking the user to save or open a json file locally

    When you install an application monitoring agent and upload a credentials csv file using Internet Explorer, the browser displays a message asking you to save or open a json file locally.  You will not be able to proceed to the next screen.

    Workaround: Use a different browser.

  • Additional cost displayed is zero even though there is a direct cost associated with the VM

    If the vCenter Server configured with vRealize Automation 8.x was already monitored by vRealize Operations Manager and costs were computed, the cost is displayed as zero.

    Workaround: Cost will match the price from the next month when both get a fresh month-to-date start.

  • Collection for the Management Pack for Microsoft Azure fails when the network connection times out

    When the Management Pack for Microsoft Azure sends a request to the Azure portal and the portal takes a longer time to read the request than the Azure SDK timeout value, collection for the adapter instance fails. Collection resumes when the network timeout issue is resolved or the Azure portal can read the request.

    Workaround: None

  • Change in the way Active Directory authentication source handles user names

    Logging in to vRealize Operations Manager with a short name will be successful only if the user name's domain suffix matches the domain name specified in the Base DN option. Otherwise, the full user name with the domain suffix is required during login. For more information, see KB 68131.

    Workaround: To authenticate using short name, configure the Active Directory authentication source to use
    samAccountName for Common Name. You must re-import the Active Directory users and groups after setting the Common Name to samAccountName.

  • Objects such as images and icons related to the Management Pack for SDDC Health, Management Pack for OpenStack, and Management Pack for SRM are not displayed 

    After you upgrade vRealize Operations Manager, if you scale a vRealize Operations Manager cluster with the Management Pack for OpenStack 5.0, or Management Pack for SRM 8.1, or Management Pack for SDDC Health 5.0 installed and add another vRealize Operations node, some objects such as images and icons related to the management packs are missing.

    Workaround: Users with an instance of the Management Pack for OpenStack, or Management Pack for SRM, or Management Pack for SDDC Health must uninstall the management packs, before upgrading vRealize Operations Manager.

  • Cost computation is not supported for a VMware Cloud vCenter Server end point in vRealize Operations Manager 8.0

    In vRealize Operations Manager 8.0, when you add a VMware Cloud vCenter Server end point and specify the cloud type as VMware Cloud on AWS, cost is not computed for the VMware Cloud vCenter Server end point, because the cost model is different from on-premises vCenter Servers.

    Workaround: The cost of infrastructure coming from VMware Cloud on AWS can be managed using the vRealize Operations Manager management
    pack for VMware Cloud on AWS.

  • Interactions in a distribution type of view, work only for the Current type of transformation

    When you create a distribution type of view and select a transformation type that is not Current, the list view is not displayed.

    Workaround: Change the selected metric transformation to Current to see the list view. You can add the same metric as an additional
    column with a relevant transformation (for example, maximum) and view the result of the transformation in the list view.

  • Alerts from the vSAN adapter that correspond to vSAN health check tests are not canceled if the test is removed from the vSAN Health Service.

    vRealize Operations Manager cannot detect and cancel deleted alerts.

    Workaround: Manually cancel the alert from the user interface of vRealize Operations Manager.

  • When using Internet Explorer 11 to access the Log Insight tab pages and dashboards, the data is blocked

    When using Internet Explorer 11 to access the Log Insight tab pages and dashboards, data is blocked, and the page remains blank.

    Workaround: Use the Firefox or Chrome browser.

  • Generated reports may be blank

    If you log in to vRealize Operations Manager with vCenter Server credentials and generate a report, the generated report is always blank.

    Workaround: None

User Interface Issues
  • The dashboard link cannot be opened when you use Internet Explorer on Windows 7

    When you try to open a dashboard that is a shared URL, the page does not open.

    Workaround: You must not use Internet Explorer with Windows 7. Open the link using other browsers.

  • The Last Year option in the date picker is not intuitive

    The Last Year option in the date picker indicates that the time range starts from the end of the previous month and goes back a year. It does not indicate a time range that spans one year from the current date or the whole previous year.

    Workaround: None

  • The filter menus in the Policies workspace step called Collect Metrics and Properties, do not work correctly

    When you deselect an option from the State, KPI, or DT drop-down menus, the filter hides all attributes irrespective of their settings.

    Workaround: Save and reopen the policy.

  • A PDF report file might not include all data from a widget that has a scrollbar

    When you generate a report that contains a custom dashboard with a widget that has a scrollbar, the downloaded PDF file might not include all the data in the widget.

    Workaround: Increase the height of the widget in the dashboard to fit all the data.