Understanding vCloud Utilization Experiences

0/5 No votes

Report this app

Description

[ad_1]

vCloud Utilization Perception is the VMware Cloud service that aggregates the information obtained from Utilization Meter and sends it to the VMware Commerce Portal initially of the next month.

The processes that occur within the cloud service embrace: aggregating the obtained information, mapping the obtained information with a license version, after which pushing it to VMware Commerce Portal.

The obtained information is saved individually by Utilization Meter UUID in an S3 bucket and ikept for for 36 months. Since Q3 2021 vCloud Utilization Perception is on the market in Cloud Companion Navigator together with different VMware services and products.

Determine 1: vCloud Utilization Perception a part of VMware Cloud Companion Navigator

What kinds of reviews does vCloud Utilization Perception assist?

The vCloud Utilization Perception service aggregates the utilization information obtained from Utilization Meter and generates the next reviews:

  1. Month-to-month Utilization Report (MUR) – Consists of data on what merchandise have been used all through the month and their related utilization. This summarized information may even be pushed to VMware Commerce Portal the place the utilization might be translated right into a Month-to-month Billing Order.
  2. vSAN Cluster Historical past – Presents details about the storage capability, license version and options utilized by a vSAN cluster.
  3. Digital Machine Historical past Report (VMH) – Supplies data on the person vRAM utilization per a VM and if it has been managed by different VMware merchandise like vROps, VCD, vRNI, and so on. or not.
  4. Buyer Month-to-month Utilization – Exhibits details about the aggregated product utilization per buyer label.

What data does the Month-to-month Utilization Report present?

The information that’s proven within the Month-to-month Utilization Report (MUR) is the full aggregated utilization related to a VMware product or a bundle of merchandise for the reporting month. Merchandise that aren’t a part of a bundle are reported as a separate line within the MUR. The next information will be seen within the report:

  • Hostname – Specifies the anonymized hostname of the product with which the utilization is related.
  • Model – Specifies the model of the product.
  • VC UUID – Exhibits the vCenter server UUID.
  • Unit of Measure – Specifies the unit of measure for the product utilization.
  • Unit to be Reported – Specified the variety of reported items.

Right here is an instance of the MUR report:

Determine 2: Month-to-month Utilization Report

What information does vSAN cluster historical past report present?

The vSAN Cluster Historical past report helps you achieve a granular view of the utilization of vSAN clusters. Any such report reveals the detected vSAN license version, the consumed storage capability and used options by a vSAN cluster.

The next data is proven within the report:

  • VC – The place of the vCenter server that seems within the Utilization Meter net utility net interface.
  • VCHostName – The title of the vCenter server with which the vSAN cluster is related. The title is anonymized.
  • vSAN ClusterId – Exhibits the cluster id.
  • vSAN ClusterName – – The vSAN cluster title, which is by default anonymized.
  • vSANLicense – The enabled vSAN license of the vSAN cluster.
  • vSAN Used (MB) – The used storage capability by a vSAN cluster.
  • From – The beginning time of the vSAN utilization by the cluster.
  • To – The top time of the vSAN utilization by the cluster.
  • Interval(hours) – Aggregated time interval for which a cluster makes use of vSAN.
  • vSANFint – Symbolize the sum of the options which have been utilized by the cluster for the time interval.

For extra data on vSAN metering and reporting, learn: Understanding vSAN Metering and Reporting.

See an instance of the report beneath:

Determine 3: vSAN Cluster Historical past Report

What information will be seen within the VMH report?

The Virutal Machine Historical past (VMH) report reveals detailed details about the consumption of vRAM of all detected vCenter server VMs by Utilization Meter.

It additionally offers data on the kind of VM (TKG, SPU, or different), if the VM is managed by vROPs, VCD, vRNI, and so on. It additionally reveals if a VM is related to a buyer label.

Here’s a detailed rationalization of every column within the report:

  • Title – Specifies the anonymized title of the VM.
  • Occasion UUID – Specifies the UUID of the VM.
  • From – The beginning time of the VM utilization.
  • To – The top time of the VM utilization
  • Interval – The interval of the VM utilization.
  • powerState – The state of the VM. At present, solely powered-on VMs are reported.
  • RAM (MB) – The vRAM used for the VM.
  • Res (MB)– The Reserved vRAM for the VM.
  • Billing (MB) – Billable reminiscence in MB.
  • MB-Hours –  Billable MB hours (MB * hrs).
  • ESXI Host Title – The anonymized title of the ESXI host with which the VM is related.
  • vSphere License – The vSphere license with which the VM is related.
  • vROps – Specifies if the VM is managed by vROPs by displaying its license version. Attainable values listed here are: S (Commonplace), A (Superior) , and E (Enterprise). If the VM is just not managed by vROps, the worth might be ‘-‘.
  • NSX – Specifies if the VM is utilizing NSX. The values point out the NSX Editions. For instance a worth of ‘A’ means the NSX version is Superior.
  • NSXFint – The int sum of the NSX options utilized by the VM. See for reference Utilization Meter 4.5 Product Detection white paper to discover ways to discover them.
  • vRNI – Specifies if the VM is managed by vRNI. The values point out the vRNI editon: A (Superior) or E (Enterprise).
  • vCD – Specifies if the VM is managed by VCD. The values embrace: True or False.
  • vmType – Specifies If the VM is Tanzu-related or not. The values right here might be: SUP, POD, TKG and Different.
  • vCF – Exhibits if the VM is managed by VCF or not. Specifies the VCF version. For instance, Commonplace w/o vSAN might be introduced as ‘S-‘.
  • Buyer Label – Specifies the title of the client label with which the VM is related.

See an instance beneath:

Determine 4: Digital Machine Historical past Report

What data does Buyer Month-to-month Utilization present?

The Buyer Month-to-month Utilization (CMR) offers data on the consumed utilization by product and buyer label. Buyer labels assist suppliers affiliate the utilization of a specific useful resource (vCenter, host, useful resource pool, and so on.) with a buyer title. For extra data, learn: Buyer Month-to-month Utilization Experiences.

The next data is introduced within the report:

  • Buyer label – Supplies the title of the client in plain textual content.
  • Product – Specifies the product which has been used and related to a buyer label.
  • Unit of Measure – Exhibits the unit of measure for the used VMware product.
  • Models to be Reported – Specifies the utilization items per VMware product and buyer label.
Determine 5: Buyer Month-to-month Utilization

Assets

Have extra questions?

Contact us at: usagemeter@vmware.com or on Slack.

[ad_2]

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.