Aria Operations Management Pack for Aggregator Shows Data and Collection Issues After Deployment

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

After deploying the Aria Operations management pack for the aggregator, multiple symptoms are observed in the environment.

1. The out-of-the-box metric Property|Hardware|vendorModel does not appear in the UI, even though it is available via API.
   
   
2. After rebooting the Aggregator, the metric appears as 'Template' in the UI instead of the correct resource name.
   
   
3. Some specified properties are being collected while others are not, despite all being available on the target child Aria Operations. Log files provide no indication for this discrepancy.
   
   
4. Supermetrics identify only as SM_<UUID> and ignore the labels="Supermetric name" configuration in the config file. This causes all supermetrics to display only as UUIDs in the UI, making them unreadable.

Environment

8.18.x

Aggregator mgmt. pack : 2.1

Cause

1. The same nameKey appears to be incorrectly used for both the template resource group and the vendor version property within this table. This duplication may be causing incorrect display name mapping.
   
   
2. The default configuration file supports this suggestion, as it does not contain any metric or property defined under the template resource group, which strongly indicates a mapping error.

Resolution

The issue is resolved in Aria Operations version 8.18.6.

Note:

However, even after an initial upgrade, the aggregator may still display super-metrics by their UUID rather than the labels specified in the configuration file.

To resolve this, the downstream source Ops must also be upgraded to version 8.18.6. Following the upgrade, you should perform an adapter redescribe on the Aggregator, then stop and restart the aggregator adapter. Once these steps were completed in our testing, the super-metrics appeared with their proper names. This confirms that both the Aggregator instance and all downstream sources must be running at least version 8.18.6.