Skip to main content
Documentation - HPE Consumption Analytics

Fields and field packages

Fields are the dimensions, measures, and tags you have collected or created in HPE Consumption Analytics platform.  While most fields are added by your collections, you can also create fields directly from the Fields page, or as part of actions in SmartTag rules.  

HPE Consumption Analytics platform organizes fields into field packages that allow you to categorize fields. This helps you easily find the fields you need when creating reports or adding widgets to your views. 

Understanding field types

HPE Consumption Analytics platform categorizes fields into three types:

  • System fields contain usage and billing data collected from your provider.  System fields map to common fields found in all service providers' data, across public cloud and HPE GreenLake services.  System fields are visually identified in the field list by the lock icon.
  • Fixed fields contain data from provider-specific fields that don't have an equivalent field in all other providers' data (for example, the Azure Meter Category and Meter Sub-Category fields), as well as tags collected from provider data.  Fixed fields are identified in the field list by the tag icon. 
  • Custom fields: are fields you create in HPE Consumption Analytics platform.  Custom fields are identified in the field list by the user icon.  See Creating custom fields and field packages for more information and steps to create your own fields.

You cannot delete System or Fixed fields from HPE Consumption Analytics platform.  You can delete Custom fields only if they are not used in HPE Consumption Analytics platform. 

For example, if you use a Custom field in a filter and a chart, you will be unable to delete that field until it is no longer used by the filter and chart.

System fields (definitions and mapping)

HPE Consumption Analytics normalizes the field names collected from cloud providers and HPE GreenLake services, so you can see cost and usage data for all sources in the same charts, reports, and insights.  For your reference, the following table defines the HPE Consumption Analytics system fields and maps them to the source fields from public cloud providers and HPE GreenLake services.

A dash (-) indicates that data for that field is not available from the cloud provider or HPE GreenLake service.

System Field Definition Source
AWS Azure Google HPE GreenLake non-metered services HPE GreenLake metered services
Account ID The account identifier for a given usage record LinkedAccountId Subscription GUID Project Number   Customer ID (e.g., HP-AMS-999-DEMO-12345)
Account Name The name of the account for a given usage record AccountName Subscription Name Project ID   Configured during onboarding
Account Owner The name of the account owner for a given usage record - Account Name Account ID   -
Account Owner ID The identifier of the account owner for a given usage record - AccountOwnerId -   -
Accounting Date The date the usage is for UsageStartDate Date (from EA) or usageEndTime (from the Azure Usage API) Based on the daily billing file - -
Accounting Month The month the usage is for          
Accounting Quarter The quarter the usage is for          
Accounting Year The accounting year the usage is for          
Capacity Free The amount of free disk capacity - - - - Free
Capacity Free Percent Percentage of free disk capacity          
Capacity Installed The amount of usable disk capacity - - - - Usable 
Capacity Units The unit of the disk capacity - - - - Configured during onboarding
Capacity Used The amount of disk used - - - - Used
Capacity Used Percent Percentage of used disk capacity          
Collection ID The identifier of a high level data feed          
Collection Name The name of a high level data feed (e.g., HPE GreenLake London Office)          
Cost A value of the Units multiplied by Rate, computed by each meter UnBlendedCost or Cost ExtendedCost The sum of Cost and Credits - -
Cost Center A a part of an organization to which costs may be charged for accounting purposes - Cost Center - - -
CPU Utilization (InstanceId) The CPU utilization of the instance CPUUtil.Average - - -
Meter ID The identifier of a homogenous group of resources used for computing a metered cost (rate x quantity) - Meter ID - Service + " " + Location + " " + Non-Metered Service Description Varies by service
Meter Name The name of a homogenous group of resources used for computing a metered cost (rate x quantity) Based on UsageType ​and ProductName in most cases Meter Name Measurement1 - -
Network In MB The Network data IN in MB on the resource ​NetworkIn (InstanceId) and NetworkBytesIn (CacheClusterId) NetworkOut.Total (Linux VMs only) - - -
Network Out MB The Network data OUT in MB on the resource NetworkOut (InstanceId) and NetworkBytesOut (CacheClusterId) NetworkOut.Total (Linux VMs only) - - -
Operating System The virtual operating system (for VM usage) Based on ItemDescription Based on Meter Sub-Category - - -
Product The name of the product consumed ProductName Product Line Item "Non-Metered Service" Varies by service
Provider The name of the company providing the consumed resource (e.g., Amazon, Azure, HPE) Set by HPE GreenLake as "Amazon" Set by HPE GreenLake as "Azure" Set by HPE GreenLake as "Google"    
Provider Region The name of the region where the resources are consumed Based on AvailabilityZone (or UsageType if AvailabilityZone is empty) Resource Location - - -
Provider Type The type of provider Set by HPE GreenLake as "Public Cloud" Set by HPE GreenLake as "Public Cloud" Set by HPE GreenLake as "Public Cloud" "Hybrid"  
Provider Zone The name of the Availability Zone where the resources are consumed (e.g., US-East-1 for AWS) AvailabilityZone Meter Region - - -
Quantity The amount of the service consumed in a given usage record UsageQuantity (or set to "1" if UsageQuantiy is empty) Consumed Quantity Measurement1 Total Consumption - -
Rate The unit cost used to compute cost UnBlendedRate or Rate ResourceRate Cost divided by Quantity - -
Read Throughput The read throughput on the resource ReadThroughput (DBInstanceIdentifier) - - - -
Resource Description The description of the usage source          
Resource ID The identifier of the usage source (e.g., A VM identifier) ResourceId Instance ID - Non-Metered Service Description Varies by service
Resource Name The name of the usage source (e.g., A VM name) Based on the Name tag (Instance Name) Based on ResourceId - Non-Metered Service Description Varies by service
Resource Type The type of resource (e.g., VM, Volume) Set by HPE GreenLake as "VM" for virtual machine records and "Volume" for storage volume records Set by HPE GreenLake as "VM" for virtual machine records - - Varies by service
Service Category The type of service consumed Based on ProductName Based on Product Based on Line Item "Non-Metered" Varies by service
Storage Read Bytes The disk or volume Read in bytes on the resource DiskReadBytes (InstanceId) and VolumeReadBytes (VolumeId) - - - -
Storage Write Bytes The disk or volume Write in bytes on the resource DiskWriteBytes (InstanceId) and VolumeWriteBytes (VolumeId) - - - -
Units The unit of measure for the usage record Based on ProductName and ItemDescription Meter Name Measurement1 Units - Varies by service
Usage End The end time (day) of a given usage record UsageEndDate Date (from EA) or usageEndTime (from the Azure Usage API) End Time - -
Usage Start The start time (day) of a given usage record UsageStartDate Date (from EA) or usageStartTime (from the Azure Usage API) Start Time - -
Usage Type The type of the usage (e.g., Consumed, Reserved)          
VM CPU Count The number of vCPU of the instance defined by the provider Based on Meter (HPE GreenLake field) Based on Meter Sub-Category - - -
VM Disk GB The amount of disk size in GB of the instance defined by the provider Based on Meter  (HPE GreenLake field) Based on Meter Sub-Category - - -
VM Disk Type The type of disk on the instance defined by the provider Based on Meter  (HPE GreenLake field) Based on Meter Sub-Category - - -
VM Family The instance family defined by the provider Based on Meter  (HPE GreenLake field) Based on Meter Sub-Category - - -
VM GPU Count The number of vGPU of the instance defined by the provider Based on Meter  (HPE GreenLake field) Based on Meter Sub-Category - - -
VM Max Num Disk The maximum number of disks that can be attached to the instance defined by the provider Based on Meter  (HPE GreenLake field) Based on Meter Sub-Category - - -
VM Memory GB The amount of memory in GB of the instance defined by the provider Based on Meter  (HPE GreenLake field) Based on Meter Sub-Category - - -
VM Provider Series The series of the instance type defined by provider Based on Meter  (HPE GreenLake field) Based on Meter Sub-Category - - -
VM Provider Type The instance type defined by the provider Based on Meter  (HPE GreenLake field) Based on Meter Sub-Category - - -
VM Size The instance size defined by the provider Based on Meter  (HPE GreenLake field) Based on Meter Sub-Category - - -
Write Throughput The write throughput on the resource WriteThroughput (DBInstanceIdentifier) - - - -

Fixed fields

There are 250+ fixed fields in HPE Consumption Analytics.  While it's not practical to include a list of all fixed fields here, when you create a report, you can view a pop-up field description for any fixed or system field, so you can better understand the data in the reports that you create.

See Service-specific field mappings for information on fixed fields defined for specific services.

Understanding the service data hierarchy

Service data has a hierarchy:

  • Device - this is the container
  • Component - this is a member within a container

Services will always have a device, but may not have components. 

In HPE Consumption Analytics, the values for device and component are mapped to the Device ID and Component ID fields, respectively.  The following table shows the hierarchy for the core services supported by HPE GreenLake:

Service Device ID Component ID Comments
3PAR and Primera Array Drive  
Apollo servers / DL servers (HPE ProLiant) Server N/A  
Azure Stack Compute Instance N/A  
Enclosure Blade (Server)  
Cloudline servers Server N/A  
Cohesity Storage Device N/A  
Cohesity Licenses Group License Type + Cluster ID  
Edgeline Device    
EL300 servers Server N/A  
Google Anthos    

 

GreenLake for Containers (CaaS) Service instance ID N/A  
GreenLake for ML-Ops Service instance ID N/A  
GreenLake for Private Cloud (VMaaS) Service instance ID N/A  
Hourly per Core Host Core  
Hyperscale Storage Device N/A  
Linux® Utilization Host Core  
Moonshot Chassis Cartridge  
Network Switch Switch Port  
Nimble Device N/A  
Nimble Volumes Array Volume  
Nutanix Host    
P2000 MSA Storage Array N/A  
Primera 2.0 Storage Device N/A  
Qumulo Device N/A  
SAN Switches (Traditional/Physical) IP address Port  
SAN Switches (Virtual Fabric) Virtual Switch ID-WWN-IP address    
SAP S/4 HANA Cloud, private edition, customer data center option Service instance ID N/A  
Scality Group-Tier/Ring N/A  
Software Licenses License Group License Type  

StoreOnce Storage (Original)

Hostname

N/A

 
StoreOnce Storage (Gen3, Gen4) Serial Number N/A  
StoreVirtual (LeftHand) Storage Storage System Disk Volume N/A  
Synergy Compute and Synergy Compute 2.0 Frame Module (Server)  
Synergy Storage Enclosure Drive  
VCMS_vCPU Host Host  
VCMS_vStorage Datastore Datastore  
Veeam Backup Storage Server Volume  
Virtual Machines / VM 2.0 (VMware, metered by Compute Unit) Host N/A  
VM Count Host N/A  
Windows Utilization Host Core  
XP Disk Arrays Array Pool/Tier  
XP 2.0 Array N/A  

 

Understanding key fields

The following are key fields used in mapping a service to fields in HPE Consumption Analytics platform usage records (most are system fields; some are fixed fields):

Field Purpose Comments Type
Resource ID Unique resource identifier for the instance that corresponds to the used and installed capacity being reported.  This will match Component ID if the service has components, otherwise Device ID. This value is unique per Account ID and Service Type (Product). System
Alt Resource ID Alternate resource ID, different from Resource ID, such as IP address, hostname, etc. Not used for all services.  Will be at the same level as Resource ID (for example, if Resource ID is Component ID, then Alt Resource ID will be at the component level). Fixed
Resource Name This is typically a more human readable version of the instance identifier.  This will match Component Name if the service has components, otherwise Device Name. This does not have to be unique, and typically includes "parent" information when the instance is a nested component (e.g., Array Name + "/" + Cage Position). System
Service Category Groups services into common categories (e.g., "Storage", "Compute").   System
Product  Specifies the name of the service (e.g., "3PAR Storage", "ProLiant Blade Servers").   System
Service Specifies a static enum for a service, e.g. "3PAR", "BL", "SAN", etc.  This field won't change, allowing the service name value in the Product field to change.   Fixed
Resource Type Refines "product". More granular than Service Category, but well-known, high-level values (e.g., "Drive", "Server", "VM", "Volume").   System

Resource Description

Further refines "product" beyond Resource Type; often used to define tiers, or may be equipment type or model (e.g., "SSD", "FC", and "NL" drive type for 3PAR, "ProLiant 660c Gen9" (model) for blades, etc.  This will match Component Description if the service has components, otherwise it will match Device Description.   Fixed
Manufacturer Populated with vendor or manufacturer May be used for hypervisor vendors (VMware, Hyper-V, etc.) Fixed
Capacity Installed Capacity Installed for services that have capacities, such as storage   System
Capacity Used Capacity Used for services that have capacities, such as storage   System
Capacity Free Capacity Free for services that have capacities, such as storage   System
Capacity Units Capacity Units for services that have capacities, such as storage   System
Status Status for services that are charged in a binary manner (e.g., on/off, online/offline, active/inactive) Note that this is at the component level for services that have components, otherwise at the device level (if the service has components, only the component status is needed). Fixed
Component ID Unique identifier for component   Fixed

Component Name

Name assigned to component during installation (e.g., blade name or hostname or serial number)

If Component Name is not available for a service, the Component ID may be used to populate this field.

Fixed

Component Description

Description of component (e.g., blade model, 3PAR drive type)

 

Fixed

Device ID Unique identifier for device   Fixed

Device Name

Name assigned to device during installation (e.g., 3PAR array name)

If name is not available for a service, the following options are used to populate this field:

  1. Hostname
  2. Serial number
  3. IP address

Fixed

Device Description Description of device (e.g., DL service model)   Fixed
Device Serial Serial number of device, if available (e.g., DL server serial number) Often the same as Device ID, but in some cases this is needed if Device ID and Device Name are already used for other fields (for example, if 3PAR Device ID is populated with the IP address and Device Name is populated with the Array Name). Fixed

Understanding field packages

HPE Consumption Analytics platform organizes fields into field packages that allow you to put fields into categories that omit irrelevant fields. This helps you easily find the fields you need when creating reports or adding widgets to your views. The All Fields package contains every field.  Most of the fields in this package are populated with values by every provider.  Fields not used by every provider (such as Department Name and Cost Center) are grouped in the Other category of the All Fields package, along with tags. This field package is maintained by HPE, and cannot be edited.

There are two other default field packages: Billing Fields and Usage Fields.  These field packages are maintained by HPE, and cannot be edited.

Billing Fields

Field Description
Account Name The name of the account for a given usage record
Accounting Date The date the usage is for
Product The name of the product consumed
Resource ID The identifier of the usage source (e.g., A VM identifier)
Provider Region The name of the region where the resources are consumed
Rate The unit cost used to compute cost
Cost A value of the Units multiplied by Rate, computed by each meter
Department Name The name of the department incurring the usage

Usage fields

Field Name Description
VM Provider Type The instance type defined by the provider
VM Family The instance family defined by the provider
VM Size The instance size defined by the provider
Operating System The virtual operating system (for VM usage)
VM CPU Count The number of vCPU of the instance defined by the provider
VM GPU Count The number of vGPU of the instance defined by the provider
VM Memory GB The amount of memory in GB of the instance defined by the provider
VM Disk GB The amount of disk size in GB of the instance defined by the provider
VM Disk Type The type of disk on the instance defined by the provider
VM Max Num Disk The maximum number of disks that can be attached to the instance defined by the provider
Resource ID The identifier of the usage source (e.g., a VM identifier)

Custom field packages

You can create other field packages that contain a subset of fields chosen by you. Your field packages can also contain groups of fields for a second level of categorization. In your packages you can change field display information, including field labels and (for numeric fields) the number of decimal places included in the displayed value. This level of control within a field package enables you to group and define packages that best suit the specific needs of your users, without altering the actual fields at the source level.  You might have several fields in HPE Consumption Analytics platform, especially if you have multiple collections for different cloud providers. To make it easier for you to find fields you have collected, you can use the Group icon to select how you want your fields to be listed: by the date they were added, by their types, or by visibility.