HPE Consumption Analytics field reference
- Last updated
- Save as PDF
Fields are the dimensions, measures, and tags that have been collected or created in HPE Consumption Analytics.
While most fields are added by your data sources, your HPE Consumption Analytics administrator can also create custom fields.
Your HPE Consumption Analytics administrator can also organize fields into field categories to help you easily find the fields you need when creating reports or adding charts to them.
Understanding key fields
The following are key fields used in mapping a service to fields in HPE Consumption Analytics usage records. Most are system fields; some are fixed fields (see Understanding field types below):
| 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:
|
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 types
HPE Consumption Analytics 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 admin users can create in HPE Consumption Analytics. Custom fields are identified in the field list by the user icon.
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 or chart, you can view a pop-up field description for any fixed or system field, so you can better understand the data in the reports and analytics you create.
System fields
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 | GCP | HPE GreenLake non-metered services | HPE GreenLake metered services | ||
| Account ID | The account identifier for a given usage record | LinkedAccountId | Subscription GUID | billing_account_id | Customer ID (e.g., HP-AMS-999-DEMO-12345) | |
| Account Name | The name of the account for a given usage record | AccountName | Subscription Name | Configured during billing account creation | ||
| Account Owner | The name of the account owner for a given usage record | - | Account Name | - | ||
| 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) | - | - | |
| 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 | cost | - | - |
| 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 | - | - | ||
| End Time | usage_end_time | |||||
| Meter ID | The identifier of a homogenous group of resources used for computing a metered cost (rate x quantity) | - | Meter ID | sku.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 | sku.description | - | - |
| 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 | service.description | "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" | |||
| Provider Region | The name of the region where the resources are consumed | Based on AvailabilityZone (or UsageType if AvailabilityZone is empty) | Resource Location | location.region | - | - |
| Provider Type | The type of provider | 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 | location.zone | - | - |
| Quantity | The amount of the service consumed in a given usage record | UsageQuantity (or set to "1" if UsageQuantiy is empty) | Consumed Quantity | usage.amount_in_pricing_units | - | - |
| Rate | The unit cost used to compute cost | UnBlendedRate or Rate | ResourceRate | - | - | |
| Read Throughput | The read throughput on the resource | ReadThroughput (DBInstanceIdentifier) | - | - | - | |
| Record type | cost_type | |||||
| Resource Description | The description of the usage source | |||||
| Resource ID | The identifier of the usage source (e.g., A VM identifier) | ResourceId | Instance ID | resource.global_name | 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 | resource.name | 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 | "Non-Metered" | Varies by service | |
| Start Time | usage_start_time | |||||
| 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 | usage.pricing_unit | - | 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) | - | - | |
| Usage Start | The start time (day) of a given usage record | UsageStartDate | Date (from EA) or usageStartTime (from the Azure Usage API) | - | - | |
| 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.
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 |
|---|---|---|
| 3PAR | Drive | Array |
| Alletra 6000 Usable | N/A | Storage system |
| Alletra 6000 Volumes | N/A | Storage system |
| Alletra 9000 NVMe | Array serial number | Device type, Device ID |
| Alletra 9000 Raw | Drive | Array |
| Alletra 9000 Usable | N/A | Array |
| Azure Stack Compute | N/A | Instance |
| Azure Stack HCI Compute | N/A | Instance |
| Azure Stack Services | N/A | Instance |
| Blades | Blade (Server) | Enclosure |
| BMaaS | N/A | Service instance ID |
| CaaS | N/A | Service instance ID |
| Catalog Lifecycle Manager | N/A | Service instance ID |
| Cloudline | N/A | Server |
| Cohesity Licenses | License type + Cluster ID | Group |
| Cohesity Storage | N/A | Cluster |
| DL Servers | N/A | Server |
| EDF Cluster | N/A | Storage system |
| Edgeline | N/A | Server |
| EL300 | N/A | Server |
| Electronic Health Record | N/A | Device |
| Google Anthos | N/A | Service |
| Hedvig | Node | Storage system |
| Hourly Per Core | Core | Host |
| HPCaaS | N/A | Service instance ID |
| Hyperscale | N/A | Hyperscale storage |
|
iLO Utilization Server On/Off |
Hostname | N/A |
|
iLO Utilization Server Per Core |
Hostname | N/A |
| LeftHand | N/A | Storage system |
| Linux® Utilization | Core | Host |
| MLOps | N/A | Service instance ID |
| Moonshot | Cartridge | Chassis |
| Network Switch | Port | Switch |
| Nimble | N/A | Storage system |
| Nimble 2.0 | Volume | Array |
| NonStop Core | Device | Device |
| Nutanix | N/A | Host |
| Nutanix 2.0 | N/A | Host |
| P2000 | N/A | Array |
| Primera | Drive | Array |
| Primera 2.0 | N/A | Device |
| Primera 3.0 | Array serial number, Device type | Device |
| Qumulo | N/A | Cluster |
| Rubrik | N/A | Cluster |
| SAN | Port | Switch |
| SAP HANA | Host | Host |
| SAP HANA 2.0 | N/A | Host |
| SAP S/4 HANA pe | N/A | Service instance ID |
| Scality | N/A | Group-Tier/Ring |
| Software Licenses | License type | License group |
| StoreOnce | N/A | Storage system |
| Synergy Compute | Module | Frame |
| Synergy Compute 2.0 | Module | Frame |
| Synergy Storage | Drive | Enclosure |
| VCMS_vCPU | N/A | Host |
| VCMS_vStorage | N/A | Datastore |
| Veeam Backup Storage | N/A | Volume |
| VM | N/A | Host |
| VMaaS | N/A | Service instance ID |
| Windows Utilization | Core | Host |
| XP 2.0 | N/A | Disk array |
| XP Disk Arrays | Pool/Tier | Array |
| XP with VMware | LDEV | Device |