Reclaimable capacity is a measurement of the CPU, memory, and disk space for your objects that is designated as waste. You can turn on and configure the settings for the Reclaimable Capacity element for the object types in your policy so that you can override the settings and have vRealize Operations Manager analyze and report on the capacity that you can reclaim from unused or underused objects. You can then provision the reclaimed capacity to other objects in your environment, based on your settings.

The Reclaimable Capacity element determines how vRealize Operations Manager reports the amount of reclaimable capacity of objects such as CPU, memory, and disk space for each object in your environment.

When you include the reclaimable capacity element in your policy, you can use the reclaimable capacity score to identify the amount of resources that can be reclaimed and provisioned to other objects.

To view and override the policy Reclaimable Capacity analysis setting, in the menu, click Administration, and then in the left pane click Policies. Click the Policy Library tab. Click the Add New Policy icon to add a policy or click the Edit Selected Policy icon to edit a policy. In the Add or Edit Monitoring policy workspace, click Analysis Settings, then select one or more objects in the left pane. The reclaimable capacity settings for the object types that you selected appear in the right pane.

View the Reclaimable Capacity policy element, and configure the settings for your policy.

If you do not configure the policy element, your policy inherits the settings from the selected base policy.

Policy Reclaimable Capacity Element Settings in the Add or Edit Monitoring Policy Workspace

Option

Description

Lock icon

Enables you to override the policy element settings so that you can customize the policy to monitor the objects in your environment.

Badge Score Symptom Threshold

Set the symptom threshold values for the policy element to levels that update the badge scores to meet the criteria for your environment. vRealize Operations Manager uses the symptom threshold values to trigger alerts that appear in the Alerts Overview and Dashboard scores.

In the menu, click Environment, and then in the left pane select an object. Click Analysis > Reclaimable Capacity to view the badge score symptom thresholds for Reclaimable Capacity policy settings for a selected object, as defined in the policy applied to the object.

Reclaimable capacity settings for resource containers

Displays the configurable percentages for vRealize Operations Manager to use to report when a resource is determined to be oversized, idle, or powered off.

In the menu, click Environment, and then in the left pane select an object. Click Analysis > Reclaimable Capacity to view the settings for disk and CPU idle levels, and the percentages used to determine when a resource is oversized, idle, or powered off for a selected object, as defined in the policy applied to the object.

For the selected object, you can set the Oversized, Idle, and Powered Off, and Unused capacity settings.

An object is considered to be oversized when its recommended capacity is less than the defined percentage of its current capacity. For example, when the Oversized setting for a virtual machine is 50%, the virtual machine is considered to be oversized when its capacity is half of the current capacity available.

An object is considered to be idle when the object operates below the idle level for the defined percentage of time. For example, when the CPU idle level is set to 100 MHz for a virtual machine, and the flag for the idle level is set to 90%, the virtual machine is considered to be idle when the speed of its CPU drops below 100 MHz for 90% of the time.

An object is flagged as powered off when the object is powered down for the defined percentage of time. For example, when the powered off flag is set to 90%, a virtual machine is flagged as powered off when it is powered down at least 90% of the time.

An object is considered to be unused when its timestamp attribute has not changed for the defined number of days, which means that the object has not been accessed. For example, when the flag for the disk space reclaimable snapshot space is set to 60 days for a virtual machine, if the virtual machine or the files on it have not been accessed for 60 days, the virtual machine is considered to be unused.