VMware Aria Operations 8.12 | 20 APRIL 2023

Check for additions and updates to these release notes.

Build Details

VMware Aria Operations 8.12 | 2023 | Build 21594884

VMware Aria Operations Upgrade PAK | 2023 | Build 21594883

Note:This upgrade .pak file includes the OS upgrade files from Photon to Photon, the vApp upgrade files, and Cloud Appliance upgrade files.

VMware Aria Operations 8.12 Pre-Upgrade Assessment Tool:

  • VMware Aria Operations Pre-Upgrade Assessment Tool for Upgrading from 8.6.x | 2023 | Build 21598390

  • VMware Aria Operations Pre-Upgrade Assessment Tool for Upgrading from 8.10.x | 2023 | Build 21598331

VMware Aria Operations Cloud Appliance (VMware Aria Operations Cloud Proxy) 8.12 | 2023 | Build 21594387

Check frequently for additions and updates to these release notes.

What's New

Read about the new and enhanced features in this release under Key Features and Capabilities.

Product Support Notice

Logs Integration Experience Change

After upgrading to VMware Aria Operations 8.12 and above, the existing Logs Integrations will stop working. For more information see the Notes in the Enhanced Logs Experience section.

vRealize Application Remote Collector

vRealize Application Remote Collector is not supported from vRealize Operations 8.10 and above. Migrate all Telegraf end points to cloud proxy before upgrading to vRealize Operations 8.10 and above. For information about migrating from vRealize Application Remote Collector to cloud proxy, see KB 83059.

vSAN Performance Data Collection

vSAN performance data collection for Virtual Machines is now deactivated by default in the vSAN adapter instance configuration settings. This change will not only apply to newly created vSAN adapter instances but also to existing ones. The change only affects the Percentage of Consumers facing Disk Latency (%) metric on vSAN type Datastore objects, which will not be calculated by default. For existing vSAN adapter instances, the metric will stop being calculated. To reactivate metric calculation, the Enable vSAN performance data collection for Virtual Machines option should be set to true from the Advanced Settings section of the vSAN adapter instance configuration.

REST Notification plug-in, SMARTS Notification plug-in, and old Email Templates

The REST Notification plug-in, SMARTS Notification plug-in, and old Email Templates available through SUITE-API have been deprecated and will be deleted in the next release of VMware Aria Operations. To continue using the functionality provided by the plug-in you will need to switch to the available alternatives listed below:

  • Old templates will be replaced by the new Email Template which is available via the product UI and the SUITE-API.

  • The REST plug-in can be replaced with the webhook plug-in.

  • The SMARTS plug-in should be replaced by VMware Aria Operations Management Pack for VMware Smart Assurance.

Key Features and Capabilities

Rebranding of vRealize Operations to VMware Aria Operations

  • In this release, we are excited to announce that vRealize Operations, VMware's powerful platform for intelligent IT operations management, has been rebranded to VMware Aria Operations. This rebranding reflects our commitment to delivering innovative solutions that help you optimize your IT operations and accelerate your digital transformation journey. With VMware Aria Operations, you can continue to rely on the same robust capabilities that vRealize Operations provided. Additionally, you can expect even more advanced features and functionality as we continue to invest in the platform. The rebranding will not impact your existing deployment of vRealize Operations. You will continue to receive the same level of support and service you have come to expect from VMware.

Enhanced Logs Experience

  • Log trend in log analysis: A new log trend feature has been added to help you better correlate metrics with logs. With this feature, you can view the trend of log messages over time, making it easier to identify patterns and anomalies.

  • Filters support for advanced troubleshooting: Added support for filters in log analysis, enabling you to quickly and easily find the relevant log messages. You can filter logs based on various criteria such as hostname, severity level, source, and time range.

  • Log fields support for log messages: Provides structure to unstructured log data by extracting key fields from log messages. You can use these fields to filter logs, as well as to create charts based on specific log fields.

  • Log Widget in Dashboards: With the new Log Widget feature in dashboards, you can complement your visual overview by accessing logs data directly within the dashboard. This helps you quickly identify and troubleshoot issues by correlating log data with performance metrics, all in one centralized location.

  • Consistent experience on all logs screens: Experience the same log experience across all log screens such as Log Analysis, Logs tab in Object browser, Logs tab in Troubleshooting workbench, and Logs widget in Dashboards.

    Notes:

    • After you upgrade to VMware Aria Operations 8.12 and above, to keep VMware Aria Operations and VMware Aria Operations for Logs Integration functional, modify the VMware Aria Operations for Logs cloud account in VMware Aria Operations and add the Credentials.

    • The VMware Aria Operations for Logs Cloud Account credentials can be configured using VMware Aria Operations for Logs Read Only local user. For more information, see Configuring VMware Aria Operations for Logs with VMware Aria Operation

Simplified User Experience with Launchpad

  • Unified use-case based UI workflow to represent both existing and new capabilities.

  • Launchpad replaces the existing Quick Start Page.

For more information, see the topic: After You Log In

VMware Cloud Foundation Operations:

  • VMware Cloud Foundation Operations allows you to view all VMware Cloud Foundation deployments along with associated management and workload domains in one place. You can also view the health of associated management applications. The health of management applications are evaluated across the following dimensions:

    • Availability, indicates if the application is reachable.

    • Virtual Machines, indicate the availability of the virtual machines on which the applications run.

    • Services, indicate the availability of all services associated with the application.

    • Certificate, indicates the validity of certificates associated with applications.

    • Passwords, indicate the validity of passwords associated with applications.

  • To use this capability, the following pre-requisites must be met:

    1. Configure VMware Cloud Foundation account in the repository.

    2. Activate VMware Infrastructure Health from the repository.

For more information, see the following topics:

Additional authentication types for webhooks

  • The following additional authentication types are supported for webhooks:

    • Bearer Token

    • OAuth

    • Certificates

    • API key

For more information, see the topic: Add a Webhook Notification Plugin for Outbound Instance.

Multi-Cloud Overview

  • Easy access and visibility of all objects that are monitored in VMware Aria Operations.

  • Provides a list of all multi-cloud and public clouds that you can monitor with a summary view of each cloud.

  • The summary view provides insights into the capacity, cost, services, and sustainability score for the selected cloud.

For more information, see the topic: Monitoring Multiple Cloud Accounts in VMware Aria Operations.

Dashboards: You can now share dashboards along with edit permissions

For more information, see the topics: Manage Dashboards and Share Dashboards with Users.

Google Cloud VMware Engine cloud account

  • Manage and monitor Google Cloud VMware Engine with a simplified and dedicated cloud account.

  • Discover Google Cloud VMware Engine and configure the adapters to monitor vCenter, vSAN, and NSX-T.

  • Traverse Google Cloud VMware Engine objects, view summary pages, configuration maximums, and get alerts for configuration maximums.

  • Plan workload migration using What-if migration scenario to migrate workload to Google Cloud VMware Engine.

  • Run compliance analysis for virtual machines against various benchmarks, optimize, and rightsize workloads.

  • Assess and plan cost based on either bill-based costing or rate card costing.

  • View dashboards to gain additional insights in Google Cloud VMware Engine environment.

For more information, see the following topics and the associated child topics:

VMware Cloud on AWS Government Cloud Account

  • Simplified management, maintenance, and administration of VMware Cloud on AWS government cloud account.

Cost Analysis

  • Conduct a cost and price analysis for your objects or groups in various management layers such as vCenter, vCloud Director, Horizon, and CloudHealth.

  • Create a graphical representation and table to compare and evaluate the gathered data.

  • Save the analysis definition to avoid repeating the process in the future.

  • Export the analysis table for offline viewing purposes.

For more information, see the following topic and the associated child topics: Cost Analysis.

Compatibility with the cluster rename feature in VMware Cloud on AWS

  • If resource pool names change due to renaming of clusters in VMware Cloud on AWS, the dashboard "VMC Management VM monitoring" has been made compatible with the new resource pool name and the jobs that are run through the automation central continues to exclude VMware Cloud on AWS management VMs.

Consolidated script for Telegraf agent installation

  • One single script for all the installation flows - product-managed, user-managed, and open-source Telegraf agent.

  • Token based approach instead of username and password for all agent types.

  • New names of the agents:

    • Product-managed agent (OS and basic services monitoring)

    • User-managed agent (Physical hosts)

    • Open-source agent (Advanced monitoring)

For more information, see the following topics:

Schedule snapshot deletion with specific name and size in Automation Central

With automation central, you now have granular controls for snapshot deletion. You may schedule snapshot deletion based on specific name and size of the snapshots.

For more information, see the topic: Create Job from Automation Central.

Workload Placement Enhancements

  • Support for allocation model in Day 2 Operations has been added and is available as a feature in this release.

  • Support for Cross Network has been added in Work Load Placement as well. Now Day 2 operations will be able to move VMs as a part of rebalancing the workloads even if the clusters are in a separate network.

For more information, see the topics:

Simplify creation and editing of collector groups and cloud proxies

  • Moved the collector groups location in the product UI to a new tab next to cloud proxies in the Data Sources page.

  • Simplified Edit and View Details for collector groups and individual cloud proxies.

  • Validation for reassigning cloud proxies already added to the current or other collector groups.

For more information, see the following topics:

Transport Node State Metric Data Collection is Deactivated

  • In the current release of VMware Aria Operations, collecting the node state through API has been deactivated by default due to performance degradation in both VMware Aria Operations and VMware NSX. However, you can still activate this feature through the policy settings, but it is not recommended as it may impact performance. Alternatively, you can collect the node state data through NSX-T Direct Alerts. This feature is still available and can be used without any performance degradation. To import NSX-T Alerts, see the topic: Alerts in NSX-T.

Capacity Management

  • Ability to select pre-defined, custom VM profiles within a scenario for what-if analysis. Simplifies scenario creation by eliminating the need to manually input VM configuration details. 

  • Ability to auto-select current date as start date on running a what-if scenario that has an outdated start date. 

    • Note:

      • End date remains unchanged. 

      • Not applicable for what-if scenarios with both start and end dates outdated.

  • Granular Settings for Conservative Risk-Level 

    • You can tune the level of conservativeness from one to five, with level 1 being the least conservative and level 5 being the most conservative. The default strength of conservativeness remains the same as in the previous releases and corresponds to level 3. Modifying the level of conservativeness will make the projection bounds narrower or wider. Higher the level, the wider the upper bound and more conservative the projections for Time Remaining, Capacity Remaining, and Recommended Size.

    • Note:

      • Rare and momentary peaks may be considered outliers and may not impact the projections even at the most conservative risk level.

      • Conservativeness strength is supported by the Conservative risk level. The Aggressive risk level produces Time Remaining, Capacity Remaining, and Recommended Size metrics always based on the mean of the projection.

Alerts Deactivation

  • An initiative is underway in VMware Aria Operations to reduce Alert noise in customer environments. As part of this release, a set of vCenter alerts have been deactivated out of the box. Get to know more about the list of deactivated alerts and the impact it has on your current environment and how to activate them on needed resources within your environment.

For more information, see the topic: Activating the Deactivated Alerts.

VMware Aria Universal Suite

When the VMware Aria Universal Suite key is applied to VMware Aria Operations, calculation of licensing/billing starts being managed by the VMware Aria Hub Subscription (SaaS) service rather than the VMware Aria Operations on-premises licensing module itself. As a result, the "License is invalid" watermark will not be displayed in the Details tabs of any unlicensed object anymore if there is any valid VMware Aria Universal Suite license key applied to VMware Aria Operations.

The status message in red about license overage will still be displayed in the Licensing section as before.

Troubleshoot faster with metric search

  • Use Global Search to search for objects using queries:

    • Use metrics, properties or super metrics associated with object types

    • Add conditions using multiple metrics and conditions

  • Auto-complete options to help build queries

  • Automatic syntax checks of the query

  • New look for search results:

    • Deep dive into metric

    • Perform roll ups

    • Launch Troubleshooting Workbench

Rest API access via Cloud Proxy

  • Allows you to access VMware Aria Operations Rest API suite via Cloud Proxy.

Cost Continuous Improvements

  • Return on Investment dashboard renamed to Cost Optimization dashboard.

  • Cost Settings renamed to Cost Drivers.

Oracle Cloud VMware Solution Cloud Account

  • Manage and monitor Oracle Cloud VMware Solution with a simplified and dedicated cloud account.

  • Discover Oracle Cloud VMware Solution SDDCs and configure the adapters to monitor vCenter, vSAN and NSX-T.

  • Traverse Oracle Cloud VMware Solution objects, view summary pages, configuration maximums and get alerts for configuration maximums.

  • Plan workload migration using the What-if migration scenarios to migrate workloads to the Oracle Cloud VMware Solution.

  • Run compliance analysis for vCenter Objects such as hosts and virtual machines against various benchmarks and review cost based on rate card costing.

  • Optimize and rightsize workloads.

For more information, see the following topics:

Automation Central Improvements

  • The following additional actions are available for scheduling:

    • Schedule public cloud actions

      • Power on, power off, reboot GCP virtual machine instance

      • Power on, power off, reboot AWS EC2 instance

      • Power on, power off, reboot Azure virtual machine

    • Schedule vSphere virtual machine actions

      • Power on VM

      • Power off VM

  • UX improvements and additional scope for selection (customer groups, custom data center, business applications, etc.) are now available.

For information, see the topic: Create Job from Automation Central.

Application Monitoring

  • Collector groups

    • Better user experience when creating collector groups.

    • View cloud proxies as a flat list or grouped by collector groups in the Data Sources → Cloud Proxies UI.

  • High Availability for Application Monitoring

    • Application Monitoring now works with collector groups.

    • You can activate or deactivate Application Monitoring high availability from the Collector Groups UI.

    • A retry mechanism when there are changes in collector groups (remove/add cloud proxy to collector group) is now available.

    For more information, see the following topics:

Bill based costing in VMware Cloud on Dell EMC

Replace web server certificate on Cloud Proxy

  • You can now replace web server certificates on port 443, used for incoming traffic to Cloud Proxy, using the cprc-cli -rc command. For more details, please refer to KB article, 89583.

    For more information, see the topic Using the Cloud Proxy Command-Line Interface.

  Certificate Monitoring

  • Certificate monitoring capability is enhanced to monitor the following components:

    • Adapters

    • Outbound Plugins

    • Authentication Sources

  • For each certificate, the following information is collected:

    • End date

    • Issuer DN

    • No. of days to expire

    • Start date

Support for monitoring VMware Cloud on AWS Outposts

  • Manage and monitor VMware Cloud on AWS Outposts using the VMware Cloud on AWS integration account.

  • Optimize capacity and performance, troubleshoot, and manage compliance for virtual machines against various benchmarks.

  • Discover VMware Cloud on AWS Outpost SDDCs and configure the adapters to monitor vCenter, vSAN, and NSX-T.

  • Traverse VMware Cloud on AWS Outpost objects and view summary pages.

For more details, see VMware Cloud on AWS Outposts.

Native Public Cloud

Sustainability

  • This feature introduces the VMWare Green Score, a score that organizations can use to track their sustainability journey, along with Power Consumption and Carbon Footprint information. Users can also view actionable insights and recommendations on how to be more sustainable in their IT operations.

    For more information, see the following topics:

    Sustainability

    Sustainability Metrics

Removal of Legacy Actions

The following actions have been removed:

  • Export Guest User Mapping Action

  • Clear Guest User Mapping Action

  • Apply Guest User Mapping Action

  • Configure Included Services Action

    You can use the Service Discovery feature instead. For more information, see Service and Application Discovery.

The NSX-T management pack supports the communication with NSX-T source via Policy APIs

  • For NSX-T versions less than 3.2.1 , existing manager APIs only will be used to communicate with NSX-T.

  • For Policy APIs to be used internally within NSX-T Adapter the following conditions need to be met.

    • NSX-T version should be >=3.2.1.

    • In NSX-T, migration coordinator should have been started. You can migrate objects created in Manager Layer of NSX-T to Policy layer. This option to promote the Manager Objects to the Policy Layer is activated only when you start the migration coordinator.

    • You should have promoted all the objects created in Manager Layer to the Policy Layer. When the migration coordinator is started, you are provided with an option to view/promote the objects that are present in Manager Layer, but are absent in the Policy layer in the NSX-T user interface.

Object Relationship Improvement in NSX-T

Object relationship has been improved to extend the Edge transport node to the virtual machine on which it is provisioned.

There are two ways to deploy Edge in NSX-T. You can either use the NSX-T Manager (auto-deployed to vCenter using NSX-T manager) or manually register the VMs to NSX-T via CLI. The manually deployed Edges are not managed by NSX-T and hence that information is not present with NSX-T. Hence, the mapping/relationship for Edge transport nodes and the Edge VM will only be for Edges deployed through the NSX-T Manager.

Upgrade of the vSphere Compliance Pack

  • Harden your infrastructure and adhere to controls as defined in the latest security configuration guide - VMware vSphere Security Configuration Guide 7 - Controls - 701-20210210-01 ​

  • Refer to KB88721 and get a comprehensive view of the newly introduced technical controls. This KB is a good source to introduce manual operational best practices for enhanced infrastructure security across your environments.

For more details, see What Are Compliance Benchmarks.

Updated Management Packs 

VMware Aria Operations for Integrations Management Packs have been updated for VMware Aria Operations 8.12.

For more information, see VMware Aria Operations for Integrations Release Notes.

Metrics and Properties Modifications

The following KB article describes all the metrics and properties that have been modified in VMware Aria Operations 8.12:

Metrics added in VMware Aria Operations 8.12

Instanced Metrics

Instanced metrics are deactivated by default after deploying or upgrading to vRealize Operations 8.2 or later, and after importing a policy from older versions. To re-activate instanced metrics in vRealize Operations 8.2 or later, see KB 81119.

Basic Authentication

Basic authentication using the REST API is deprecated and deactivated in VMware Aria Operations 8.12 fresh deployments by default. Instances that have been upgraded to VMware Aria Operations 8.12, will inherit the same properties before the upgrade. It is recommended that you use token-based authentication instead. If you still need to activate or deactivate basic authentication, see KB 77271.

Active Directory Authentication Sources

Logging in to VMware Aria Operations 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

System Requirements

Review this section before you install or update VMware Aria Operations.

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 VMware Aria Operations 8.12 with VMware virtual appliance.

If you are deploying a VMware Aria Operations virtual appliance and VMware Aria Operations Cloud Appliance (cloud proxy), use a VMware vSphere Client to connect to a VMware vCenter Server, and deploy the virtual appliance through the vCenter Server instance. The VMware Aria Operations virtual appliance and VMware Aria Operations Cloud Appliance (cloud proxy) must be deployed on hosts that are:

  • ESX/ESXi 6.5 Update 1 or later and managed by VMware vCenter Server 6.5 or later.

  • If you have VMware Aria Operations virtual appliance deployed on ESXi 6.0 or older hosts, you must first upgrade vCenter Server and ESXi to version 6.5 Update 1 or later, and then upgrade to VMware Aria Operations 8.12.

Hardware Versions, Cipher Suites and Protocols, and Log4j

Hardware Versions

The minimum hardware version required for VMware Aria Operations 8.x releases is version 11. If your VMware Aria Operations virtual appliance had a hardware version earlier than 11, you must first upgrade to hardware version 11 on VMware Aria Operations virtual appliance and then upgrade to VMware Aria Operations 8.12.

Cipher Suites and Protocols

For information about cipher suite lists and relevant protocols, see Cipher Suites and Protocols.

Log4j version is at 2.17.2.

VMware Product Compatibility

VMware Product Compatibility

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

Note: For FIPS mode compatibility details, see the footnotes in the interoperability matrix. The product will not work in FIPS mode if there are footnotes that state that it will not work in FIPS mode.

Solutions and Browser Support

Solutions Support

In addition to the VMware solutions (vSphere, VMware Aria Operations for Logs, vSAN, Service Discovery, NSX-T, and many more), see the VMware Marketplace for many more solutions. These solutions work with Virtual Appliance single or multiple nodes.

Browser Support

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

  • Google Chrome: Versions 111 and 112

  • Mozilla Firefox: Version 111.0.1

  • Microsoft Edge: Versions 110 and 111

  • Safari: 16.3

Note: Support for Internet Explorer has been dropped from vRealize Operations 8.4 onwards.

SDDC Compliance

Ensure compliance of your vSphere, vSAN, and NSX-T resources deployed across private data centers, and other VMware Managed Clouds such as VMware Cloud Foundation (VCF), VMware Cloud on AWS, Azure VMware Solution, Google Cloud VMware Engine, Oracle Cloud VMware Solution, and VMware Cloud on Dell EMC using various compliance packs in VMware Aria Operations. For information about supported versions of vSphere, vSAN, and NSX-T, see the VMware Product Interoperability Matrix.

VMware Aria Operations 8.12 includes compliance alerts for the VMware vSphere 7 Security Configuration Guide and does not include the rule set for vSphere Secure Configuration Guide 7 Update 3.

Installing and Upgrading VMware Aria Operations

Upgrading to VMware Aria Operations 8.12, resets out-of-the-box content as part of the software upgrade process. 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 VMware Aria Operations 8.12.

Notes:

  • To see the supported direct upgrade path, refer to the Product Interoperability Matrix.

  • While upgrading to VMware Aria Operations 8.12, the expected size of the /dev/sda for Photon OS is 20 GB (hard disk 1). For information about this requirement, see KB 75298.

  • It is always recommended to run the Pre-Upgrade Assessment tool before an upgrade. 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.

    • To run a pre-upgrade assessment on 8.6.x setups, you must download the “VMware Aria Operations Pre-Upgrade Assessment Tool for Upgrading from 8.6.x” PAK file.

    • To run a pre-upgrade assessment on 8.10.x setups, you must download the “VMware Aria Operations Pre-Upgrade Assessment Tool for Upgrading from 8.10.x” PAK file.

      For more details on using the Pre-Upgrade Assessment Tool, see KB 91693.

VMware Aria Suite Lifecycle 8.12 supports the installation of VMware Aria Operations 8.12. For more information, see the VMware Aria Suite Lifecycle 8.12 Release Notes.

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

The VMware Aria Operations Information Center has detailed information about installation and software updates.

Refer to the Getting Started with VMware Aria Operations Guide that provides guidance for a VMware Aria Operations virtual appliance, before you install or update VMware Aria Operations.

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

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

Note: You can also install VMware Aria Operations by using VMware Aria Suite Lifecycle Manager. For more information, see the VMware Aria Suite Lifecycle Installation, Upgrade, and Management Guide.

Resolved Issues

For details on resolved issues, see KB 91691.

  • Telegraf agent related operations fail as ports 4505 and 4506 are not reachable

    Salt ports 4505 and 4506 become unreachable while performing Telegraf agent related operations.

Known Issues

Installation and Upgrade Issues

  • Upgrade to VMware Aria Operations 8.12 will impact some management packs

    When you upgrade to VMware Aria Operations 8.12, some management packs might not be compatible with JDK11 and would require an upgrade to a JDK11 compatible version. Contact the vendor to confirm if the management pack is compatible with VMware Aria Operations 8.12.

    Workaround: See KB 89675 for more details.

  • The PAK file upload process is slower in VMware Aria Operations 8.12

    The VMware Aria Operations 8.12 upgrade PAK file may take longer to upload and may sometimes not complete uploading if you are using Firefox as a browser through a high latency network.

    Workaround: Use another supported browser to upload the PAK file and start upgrading to VMware Aria Operations 8.12.

  • After you upgrade vRealize Operations from 8.4 to a later release, content upgrade and agent management actions fail

    After you upgrade from a previous release, content upgrade and agent management actions fail on on-prem and SaaS when you also upgrade cloud proxy.

    Workaround:

    Complete the following steps:

    1. SSH to the Cloud Proxy VM.

    2. Run the following command: /rpm-content/ucp/subsequentboot.sh

    You can view the log from the following location: /opt/vmware/var/log/ucp-subsequentboot

  • 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 VMware Aria Operations 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

  • VMware Aria Operations API (Suite-API) based Telegraf agent installation fails with an error

    When you use an API end point for Telegraf agent installation in VMware Aria Operations API (Suite-API) using /api/applications/agents, the following error occurs:

    VM with ID - id is not connected to any ARC or Cloud Proxy
Ex- VM with ID - 94b8e2eb-37fa-4a44-b241-b50e3a013bf7 is not connected to any ARC or Cloud Proxy

    Workaround:

    1. Move the vCenter adapter collector/group back to the same cloud proxy/collector group that was selected the during the first Telegraf agent installation of VMs for that vCenter.

    2. Navigate to Data Sources > Integrations > Accounts > vCenter and select the vCenter where the endpoint is located.

    3. Click Edit and under the Cloud Account Information, select the vCenter tab > Collector/Group and change collector/collector group from drop down options and then click Save.

    4. After the Telegraf agent installation is successful, move the vCenter adapter collector/group back to the initial cloud proxy/collector group.

  • Agent install fails with the error: Connect to salt master

    When you install an agent to monitor applications using Telegraf, the following error may occur: Connect to Salt Master. The error occurs because the end point VM is unable to connect with the salt master.

    Workaround: Verify the ownership of the folders in /ucp/salt/pki/master in cloud proxy. The ownership must be admin/admin. If the ownership is not admin, reset permissions/ownership.

    1. Run the /ucp/ucp-config-scripts/ucp-firstboot.sh script and verify the permissions of the folder.

    2. Reinstall the agent after successful execution of the script.

    Agent install should be successful.

  • JBoss server running in domain mode does not support LCM using custom Telegraf

    You cannot deploy jolokia.war across all the servers that run as a part of the JBoss domain mode and hence metrics cannot be collected.

    Workaround: Monitoring domain mode configuration in JBoss is supported in open source Telegraf. You can deploy jolokia.war across multiple servers.

  • The Add button in the Manage Telegraf Agents page remains activated after the creation of an application service

    While monitoring specific application services using Telegraf, the Add button in the Manage Telegraf Agents page is active after the creation of the second instance of the following application services: MSIIS, Active Directory, SharePoint, MSExchange, and Network Time Protocol.

    Workaround: Delete the previous configurations of the specific application services and configure a new one.

  • Concurrent activation or deactivation of plugins during application monitoring using suite-api does not work

    During application monitoring using suite-api, when you activate or deactivate plugins concurrently, plugin activation or deactivation does not work. An exception is logged in the ucpapi.log file.

    Workaround: Provide a gap of one second between each thread during activation or deactivation of the plugins using suite-api.

  • When you get an application instance's configuration status using a Rest-API call, a wrong status is returned when the same configuration was installed or uninstalled previously

    If you installed or uninstalled an application instance and then uninstalled or installed it respectively, the API returns "SUBMITTING" when you try to get the application instance install or uninstall configuration status using "GET /api/applications/agents/services/{taskId}/status".

    Workaround: While getting the application instance configuration status using the "GET /api/applications/agents/services/{taskId}/status" API, ensure that you use the latest performed task ID. The result of calls with older IDs is undefined.

  • When you upgrade from vRealize Operations 8.1 to VMware Aria Operations 8.12, the Cassandra application service is displayed as Java Application in the Services Discovered/Configured column of the Manage Telegraf Agents tab

    During application monitoring, after you upgrade from vRealize Operations 8.1 to VMware Aria Operations 8.12, the Cassandra application service is displayed as Java Application in the Services Discovered/Configured column of the Manage Telegraf Agents tab. This happens if the Cassandra application service is configured for monitoring in vRealize Operations 8.1, using the vRealize Application Remote Collector generic Java plugin.

    Workaround: Deactivate the Java plugin before you upgrade the vRealize Application Remote Collector agent on the VM. After upgrading the vRealize Application Remote Collector agent, the Cassandra plugin will be discovered and can then be activated.

  • System language settings affects service discovery

    Service discovery might not work if the system language is different from English. For languages different from English, network connection state values might be different from constants defined in standard RFCs.

    Workaround: None

  • Reconfigure the Project Price widget if the VMware Aria Automation integration is deactivated and then reactivated

    There is data missing in the Project Price widget of the Cloud Automation Project Price Overview dashboard when you deactivate and then reactivate an existing VMware Aria Automation integration.

    Workaround: Reconfigure the Project Price widget by completing the following steps:

    1. After you deactivate and then reactivate the VMware Aria Automation integration, navigate to Dashboards > VMware Aria Automation > Cloud Automation Project Price Overview dashboard.

    2. Edit the Project Price widget.

    3. Navigate to the Input data section.

    4. Select the '+' (Add Object) button and select the CAS World object from VMware Aria Automation > CAS World.

    5. Click OK.

    6. Navigate to the Output data in the same widget configuration mode. Search for and select the CAS Project Price View object from the list.

    7. Save the widget.

  • 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 VMware Aria Operations 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.

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

    VMware Aria Operations cannot detect and cancel deleted alerts.

    Workaround: Manually cancel the alert from the user interface of VMware Aria Operations.

  • Despite deleting ucp-adapter instance certificates, users can run actions

    If users delete ucp-adapter instance certificates, they can still run actions such as, start and stop an agent, configure remote checks, and so on.

    Workaround: None

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

      If that set is activated 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.

User Interface Issues

  • After upgrading cloud proxy and VMware Aria Operations to 8.12, the VM name is not appended to the MSSQL instance

    After upgrading cloud proxy and VMware Aria Operations to 8.12, the VM name is not appended to the MSSQL instance for existing or newly activated plugins.

    Workaround: None

  • 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

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

check-circle-line exclamation-circle-line close-line
Scroll to top icon