Enabling super metric in a policy does not work for previously deleted and imported super metric in vRealize Operations(Aria Operations)

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

Imported supermetric may not be enabled in the policy if the following steps are taken in vRealize Operations(Aria Operations)

1. Create supermetric
2. Enable supermetric policy.
3. Export supermetric.
4. Delete supermetric
5. Import supermetric.
6. Enable the super metric in the needed policy by editing it from the Super Metrics page.

 

Environment

VMware vRealize Operations 8.x

Cause

When deleting the super-metric from vROps it updates the in-memory policy cache, but the super-metric state in Policy DB is not reset immediately. Instead, Policy DB updates every 24 hours – aggregating all changes during that time window. Because of this, if super-metric is imported right after the deletion, it’s state in the Policy DB remains unchanged (i.e. Manually Enabled). Generally, vROps in-memory policy cache is updated based on Policy DB change triggers. Because of there is no change in the database, vROps in-memory caches do not get updated accordingly.

Resolution

There is no permanent solution so far.

Workaround:

To work around this issue, use one of these options

-Import supermetric 24 hours after deleting it, as the policy DB is updated every 24 hours
-Enable it on policy edit page instead of supermetric edit page.
 

Additional Information

Impact/Risks:

Unable to collect data using the imported super metric