When migrating vCenter Operations Manager 5.x to this version, you familiarize yourself with the transformations that occur when vRealize Operations Manager creates the migrated set of policies.

The relationship between policies and attribute packages is very different in vCenter Operations Manager 5.x and this version.

When vRealize Operations Manager creates migrated policies per 5.x attribute packages, the following transformations are necessary:

Merge all All Attributes for all resource kinds into one policy.

Merge all Default Attributes for all resource kinds into one policy.

Create one policy per custom, user-created attribute package.

vRealize Operations Manager transforms metric states depending on whether the metric is monitored:

Any collected metric in an attribute package is enabled in the corresponding policy.

Any metric that is not collected is disabled in the corresponding policy.

vRealize Operations Manager migrates key performance indicators (KPIs), symptom definitions, and alert definitions. For any such metric in an attribute package, the following transformations are necessary:

If there is any hard threshold specified for the metric:

If a matching hard threshold based symptom definition with the same metric, criticality, and operator exists in the new version, enable the symptom definition and override the threshold in the corresponding policy.

Otherwise, create a new symptom definition, and enable the symptom definition in the corresponding policy.

If Violation Of Hard Threshold Is A Key Indicator or Select Criticality Level At Which A Hard Threshold Becomes Key Indicator is enabled:

Mark the metric as a KPI in the corresponding policy.

Create alert definitions for any hard threshold symptom definitions created or found in the previous steps, and enable the alert definitions in the corresponding policy.

If Violation Of The Upper Dynamic Threshold Is A Key Indicator is enabled:

Mark the metric as a KPI in the corresponding policy.

if a matching dynamic threshold based symptom definition exists, enable the symptom definition in the corresponding policy.

Otherwise, create a dynamic threshold based symptom definition and enable the symptom definition in the corresponding policy:

operator = DT_VIOLATION (if both flags are on)

operator = DT_ABOVE (if only the first flag is on)

operator = DT_BELOW (if only the second flag is on)

Create alert definitions from the dynamic threshold based symptom definition created or found in the previous steps, and enable the alert definitions in the corresponding policy.