Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Reclaimable|Oversized VMs metrics removed in vRealize Operations Manager 7.0 (67267)

Last Updated: 3/5/2019Categories: TroubleshootingTotal Views: 5253Language:
Chinese (Simplified)JapaneseEnglish

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

The Cluster Compute Resource metrics, Reclaimable|Oversized VMs|CPU (vCPUs) and Reclaimable|Oversized VMs|Memory (Kb), are not collecting, despite being enabled in the policy.

The view Reclaimable Resources from Oversized VMs in a cluster contains no data.

The reports Reclamation Report - vSphere Clusters, and Reclamation Report - Environment contain no data under the Reclaimable Resources from Oversized VMs section.

Cause

The Reclaimable|Oversized VMs|CPU (vCPUs) and Reclaimable|Oversized VMs|Memory (Kb) metrics for Cluster compute resources introduced in vRealize Operations Manager 6.7 have been removed in vRealize Operations Manager 7.0.

Oversized VMs have been removed from the reclaimable concept, and moved to Rightsizing in vRealize Operations Manager 7.0.

Resolution

To resolve issues with content using the Reclaimable|Oversized VMs|CPU (vCPUs) and Reclaimable|Oversized VMs|Memory (Kb) metrics for Cluster compute resources, replace the metrics with custom Super Metrics.

To create the Super metrics, you must have vRealize Operations Manager Advanced, or Enterprise.

Log into the vRealize Operations Manager UI as an administrator.

Navigate to Administration > Configuration > Super Metrics.

Click Add New Super Metric.

Enter Reclaimable CPU (vCPUs) for the Name.

Copy and Paste the below formula into the formula field:

sum(${adaptertype=VMWARE, objecttype=VirtualMachine, metric=summary|oversized|vcpus, depth=2})

Click Save.

Under Object Types, click Add Object Type.

Filter for Cluster Compute Resource and select that entry under vCenter Adapter, then click Select.

Repeat steps 3-8 to create a Super Metric named Reclaimable Memory (Kb) with the bellow formula:

sum(${adaptertype=VMWARE, objecttype=VirtualMachine, metric=summary|oversized|memory, depth=2})/1048576

Navigate to Administration > Policies > Policy Library.

Select the desired Policy and click Edit Selected Policy.

Under section 5. Collect Metrics and Properties, filter for Reclaimable CPU (vCPUs).

Select the Super Metric Type entry created in steps 3-8 for the Object Type of Cluster Compute Resource, and change the State to Local Enabled.

Repeat steps 12-13 for the Reclaimable Memory (Kb) Super Metric.

Click Save.

The Super Metrics will begin collecting within a few collection cycles.

Replace the Reclaimable|Oversized VMs|CPU (vCPUs) and Reclaimable|Oversized VMs|Memory (Kb) metrics used in a copy of the Reclaimable Resources from Oversized VMs in a cluster View with the newly created Super Metrics.

Navigate to Dashboards > Views.

Filter for Reclaimable Resources from Oversized VMs in a cluster, then select the entry and click Clone View.

Rename the cloned View if desired.

Click Remove next to the metrics located under the Data tab.

Click 4. Data to expand the data section.

Filter for Reclaimable CPU (vCPUs).

Drag the Super Metric into the Data field on the right.

Repeat steps 5-6 for the Reclaimable Memory (Kb) Super Metric.

Click Save.

Replace the View used in the Reclamation Report - vSphere Clusters, and Reclamation Report - Environment reports with the cloned View.

Navigate to Dashboards > Reports.

Filter for Reclamation Report - vSphere Clusters, then select the entry and click Clone Template.

Rename the cloned report if desired.

Click Remove next to the Reclaimable Resources from Oversized VMs in a cluster View in the main panel.

Click 2. Views and Dashboards to expand the section.

Set Data Type to Views, and filter for the cloned View you created in the previous section.

Drag the cloned View into the field on the right between Reclaimable Resources from Idle VMs in a cluster and Reclaimable Resources from Powered Off VMs in a cluster.

Click Save.

Repeat steps 2-8 for the Reclamation Report - Environment report.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Operations Manager

VMware vRealize Operations

Related Versions:

VMware vRealize Operations Manager 7.0.x

Take Our Survey

Support Assistant