Overview
This document outlines the definitions used in the Optical Prime General Excel. All capacity values are calculated per base 2 (1024).
Details Tab
Field |
Description |
Project ID |
The project ID |
Project Name |
The project Name |
Date |
The creation date for the project in YYYY/MM/DD format. |
Owner |
The first and last name of the project owner with the email address in parenthesis. |
Collector Build Version |
The build version of the collector that generated the first Collector Run in this project. |
Glossary Knowledge Base Article Link |
URL to the Glossary for this spreadsheet to be provided by TPM before release. |
Spreadsheet Version |
The build version of the code that generated the spreadsheet. |
Servers Tab
Each row in this worksheet represents a server that is not a hypervisor. Note: desktop systems also included in this worksheet. If a user targeted Optical Prime directly at a virtual machine, that system will also show up in this sheet.
Field |
Description |
Server Name |
The name of the server. Usually this is the hostname, but sometimes this is the full DNS name, and rarely this can just be an IP address of the server. |
OS |
The full operating system name as reported by the OS |
Manufacturer |
The manufacturer of the physical server (hardware) |
Model |
The model number of the physical server (hardware) |
CPU Sockets |
The total number of CPU sockets (CPU packages) running on this server. Note: This only represents the running CPU sockets. If a socket is not equipped with a CPU or is otherwise disabled in the BIOS. That socket will not be included in this count. |
CPU Cores |
The total number of CPU cores running on this server. |
CPU Description |
The manufacturer and model information of the CPU type installed on this server |
Net Clock Speed (GHz) |
The sum of the clock speed for each CPU core running on this server measured in GHz |
CPU Clock Speed (GHz) |
The clock speed of each individual CPU core running on this server measured in GHz |
Peak CPU Percentage |
The peak CPU used by the server reported as a percentage of all of the CPU cores running on the server covering the entire duration of the real-time collection Notes: 100% indicates that all CPU cores on the server were completed saturated. |
Total CPU Hours |
The total number of hours of CPU telemetry observed on this server rounded down to the nearest integer |
Idle CPU Hours |
The number of hours of CPU telemetry observed on this server where the CPU utilization never exceeded 8% based on a two-minute sampling period. This value is rounded down to the nearest integer. |
Memory (KiB) |
The provisioned server RAM memory in kilobytes |
Peak Memory Usage (KiB) |
The peak memory used by the server measured in kilobytes covering the entire duration of the real-time collection |
Local Capacity (GiB) |
The total size of any disk storage local to this server |
Free Capacity (GiB) |
The unused portion of disk storage local to this server as defined in Local Capacity above |
Used Capacity (GiB) |
The used portion of disk storage local to this server as defined in Local Capacity above |
Average IOPS |
The original column name is IOPS. |
Peak IOPS |
The peak IO operations per second (combining read and write operations) for this server to and from all storage attached to this server for the entire duration of the real-time collection |
95% IOPS |
The IO operations per second (combining read and write operations) for this server to and from all storage attached to this server for the entire duration of the real-time collection at the 95th percentile of the peak. |
Avg. Read Latency |
The original column name is Read Latency (ms) |
Avg. Write Latency |
The original column name is Write Latency (ms) The average latency reported in milliseconds for write operations issued by the server for the entire duration of the real-time collection |
Peak Read Latency |
The peak latency reported in milliseconds for reads issued by the server for the entire duration of the real-time collection Notes: This latency is calculated at the system level of the server as an average of operations for each 2 minute sampling period. Therefore, it is possible that an individual disk might have encountered a higher or lower peak latency for the period for a given operation. |
Peak Write Latency |
The peak latency reported in milliseconds for writes issued by the server for the entire duration of the real-time collection Notes: This latency is calculated at the system level of the server as an average of operations for each 2 minute sampling period. Therefore, it is possible that an individual disk might have encountered a higher or lower peak latency for the period for a given operation. |
Queue Depth |
The average queue depth for all IO to this sever for the entire duration of the real-time collection |
Peak Throughput MB/s |
The original column name is MB/s. The peak (read and write) disk data rate from the server measured in megabytes per second for the entire duration of the real-time collection |
Avg. Throughput MB/s |
The average (read and write) disk data rate from the server measured in megabytes per second for the entire duration of the real-time collection |
Read/Write Ratio |
The average read and write ratio as a percentage covering the time records when the IOPS for the server were >= to the 90th percentile IOPS Notes: This is not the average read/write ratio for the entire duration of the real-time collection. It is only the average for the top 10% of records by IOPS. In other words, when the server was at it’s busiest, this is the read/write ratio. |
IP1 |
The first IP address assigned to this server |
IP2 |
The second IP address assigned to this server (if any) |
Serial No. |
The service tag or serial number of the physical server (hardware) of this host Note: If this is a blade server, this should be the service tag for the blade server itself (not the chassis). |
GPU Tab
Each row in this tab represents an individual GPU.
Note: a single server may have more than one GPU and thus will have more than one row entry.
Field |
Description |
GPU |
The manufacturer and model of the GPU |
OS |
The full operating system name for the server on which this GPU is installed |
Serial No. |
The service tag or serial number of the physical server (hardware) of this host Note: If this is a blade server, this should be the service tag for the blade server itself (not the chassis). |
Server Name |
The name of the server to which this GPU belongs. Usually this is the hostname, but sometimes this is the full DNS name, and rarely this can just be an IP address of the server. |
Hypervisors Tab
Each row in this worksheet represents a hypervisor that is hosting one or more virtual machines.
Fields |
Description |
|
Server Name |
The name of the hypervisor Note: Usually the DNS name, but sometimes just an IP address |
|
Datacenter |
The name of the virtual datacenter that contains this hypervisor. |
|
Cluster |
The name of the cluster that contains this hypervisor. |
|
OS |
The full operating system name as reported by the OS |
|
Manufacturer |
The manufacturer of the physical hypervisor (hardware) |
|
Model |
The model number of the physical hypervisor (hardware) |
|
CPU Sockets |
The total number of CPU sockets (CPU packages) running on this hypervisor. Note: This only represents the running CPU sockets. If a socket is not equipped with a CPU or is otherwise disabled in the BIOS, then that socket will not be included in this count. |
|
CPU Cores |
The total number of CPU cores running on this hypervisor. |
|
CPU Description |
The manufacturer and model information of the CPU type installed on this hypervisor |
|
Net Clock Speed (GHz) |
The sum of the clock speed for each CPU core running on this hypervisor measured in GHz |
|
CPU Clock Speed (GHz) |
The clock speed of the CPU measured in GHz |
|
Peak CPU Percentage |
The peak CPU used by the hypervisor reported as a percentage of all of the CPU cores running on the hypervisor covering the entire duration of the real-time collection Notes: 100% indicates that all CPU cores on the server were completed saturated. This field should fall within a range of 0 - 100%. |
|
Total CPU Hours |
The total number of hours of CPU telemetry observed on this server rounded down to the nearest integer |
|
Idle CPU Hours |
The number of hours of CPU telemetry observed on this server where the CPU utilization never exceeded 8% based on a two-minute sampling period. This value is rounded down to the nearest integer. |
|
Memory (KiB) |
The provisioned hypervisor RAM memory in kilobytes |
|
Peak Memory Usage (KiB) |
The peak memory used by the hypervisor measured in kilobytes covering the entire duration of the real-time collection |
|
Local Capacity (GiB) |
The total size of any disk storage local to this hypervisor |
|
Free Capacity (GiB) |
The unused portion of disk storage local to this hypervisor as defined in Local Capacity above |
|
Used Capacity (GiB) |
The used portion of disk storage local to this hypervisor as defined in Local Capacity above |
|
Average IOPS |
The original column name was IOPS. The average IO operations per second (combining read and write operations) for this hypervisor to and from all storage attached to this hypervisor for the entire duration of the real-time collection |
|
95% IOPS |
The IO operations per second (combining read and write operations) for this hypervisor to and from all storage attached to this hypervisor for the entire duration of the real-time collection at the 95th percentile of the peak (Note: Live Optics uses the nearest rank algorithm for calculating percentiles unless otherwise noted.) |
|
Peak IOPS |
The peak IO operations per second (combining read and write operations) for this hypervisor to and from all storage attached to this hypervisor for the entire duration of the real-time collection |
|
Avg. Read Latency |
The original column name was Read Latency (ms) The average latency reported in milliseconds for read operations issued by the hypervisor for the entire duration of the real-time collection |
|
Avg. Write Latency |
The original column name was Write Latency (ms) The average latency reported in milliseconds for write operations issued by the hypervisor for the entire duration of the real-time collection |
|
Queue Depth |
The average queue depth for all IO to this hypervisor for the entire duration of the real-time collection |
|
Peak Throughput MB/s |
The original column name was MB/s. The peak (read and write) disk data rate from the hypervisor measured in megabytes per second for the entire duration of the real-time collection |
|
Avg. Throughput MB/s |
The average (read and write) disk data rate from the hypervisor measured in megabytes per second for the entire duration of the real-time collection |
|
Read/Write Ratio |
The average read and write ratio as a percentage covering the time records when the IOPS for the server were >= to the 90th percentile IOPS Notes: This is not the average read/write ratio for the entire duration of the real-time collection. It is only the average for the top 10% of records by IOPS. In other words, when the server was at it’s busiest, this is the read/write ratio. |
|
Guest VM Count |
The total number of guest virtual machines that are on this hypervisor Note: This includes running and non-running guest virtual machines. |
|
Number of NICs |
The total number of network interface connection ports on the physical hypervisor host |
|
Number of HBAs |
The total number of storage host bus adapters installed on the physical hypervisor host. Note: if blank, then this value was not accessible to the Live Optics collector. |
|
IP1 |
The first IP address assigned to this host |
|
IP2 |
The second IP address assigned to this host (if any) |
|
Serial No. |
The service tag or serial number of the physical server (hardware) of this host Note: If this is a blade server, this should be the service tag for the blade server itself (not the chassis). |
|
Config Status |
The overall status of the ESXi host as known by vCenter. (This value will only be present if the hypervisor is VMware.) gray - the status is unknown to vCenter |
|
Boot Time |
The date and time when the hypervisor host was last booted. (This value will only be present if the hypervisor is VMware.) |
|
Server DisksTab
Each row in this worksheet represents a local disk connected to a server, desktop, or hypervisor. (Note: if a virtual machine was directly targeted by the user, then disks attached to that virtual machine will be listed here.)
Field |
Description |
Server Name |
The name of the server to which this shared cluster disk is attached |
Device Name |
The name of the shared cluster disk |
Capacity (GiB) |
The size of the shared cluster disk measured in gigabytes |
Free Capacity (GiB) |
The free capacity on this shared cluster disk measured in gigabytes. (Note: if the free capacity is zero, then likely the Live Optics collector was unable to ascertain the actual usage on the disk.) |
Used Capacity (GiB) |
The portion of the shared cluster disk capacity that currently is in use measured in gigabytes. |
95% IOPS |
The IO operations per second (combining read and write operations) for this disk from this server for the entire duration of the real-time collection at the 95th percentile of the peak. (Note: Live Optics uses the nearest rank algorithm for calculating percentiles unless otherwise noted.) |
Peak IOPS |
The peak IO operations per second (combining read and write operations) for this disk from this server. |
Avg. Read Latency |
The original column name was Read Latency (ms) The average latency reported in milliseconds for read operations issued by the disk for the entire duration of the real-time collection from this server |
Avg. Write Latency |
The original column name was Write Latency (ms) The average latency reported in milliseconds for write operations issued by the disk for the entire duration of the real-time collection from this server |
Queue Depth |
The average queue depth for all IO to this hypervisor for the entire duration of the real-time collection from this server |
Read/Write Ratio |
The average read and write ratio as a percentage covering the time records when the IOPS for this disk were >= to the 90th percentile IOPS from this server Notes: This is not the average read/write ratio for the entire duration of the real-time collection. It is only the average for the top 10% of records by IOPS. In other words, when the disk was at it’s busiest, this is the read/write ratio. |
Vendor |
This value is only present if this disk is part of a VMware deployment. The disk vendor name |
Model |
This value is only present if this disk is part of a VMware deployment. The disk model name |
Lun Type |
This value is only present if this disk is part of a VMware deployment. One of these possible values: disk, tape, cdrom, communications, enclosure, mediaChanger, opticalDevice, printer, processor, scanner, storageArrayController, unknown, or worm |
SCSI Level |
This value is only present if this disk is part of a VMware deployment. The supported SCSI protocol level version for SCSI primary commands (an integer value ranging from 2 - 6) |
vStorageSupport |
This value is only present if this disk is part of a VMware deployment. vStorage hardware acceleration support status. If a storage device supports hardware acceleration, the ESXi host can offload specific virtual machine management operations to the storage device. With hardware assistance, the host performs storage operations faster and consumes less CPU, memory, and storage fabric bandwidth. |
Datacenter |
This value is only present if this disk is part of a VMware deployment. The name of the virtual datacenter that contains this ESXi host |
Cluster Disks Tab
Each row in this worksheet represents a shared cluster disk connection to a server, desktop, or hypervisor. (Note: if a virtual machine was directly targeted by the user, then disks attached to that virtual machine will be listed here.)
Each shared cluster disk will show up with multiple rows in this spreadsheet: one row for each server to which the cluster disk is connected.
Field |
Description |
Server Name |
The name of the server to which this shared cluster disk is attached |
Device Name |
The name of the shared cluster disk |
Capacity (GiB) |
The size of the shared cluster disk measured in gigabytes |
Free Capacity (GiB) |
The free capacity on this shared cluster disk measured in gigabytes. (Note: if the free capacity is zero, then likely the Live Optics collector was unable to ascertain the actual usage on the disk.) |
Used Capacity (GiB) |
The portion of the shared cluster disk capacity that currently is in use measured in gigabytes. |
95% IOPS |
The IO operations per second (combining read and write operations) for this disk from this server for the entire duration of the real-time collection at the 95th percentile of the peak. (Note: Live Optics uses the nearest rank algorithm for calculating percentiles unless otherwise noted.) |
Peak IOPS |
The peak IO operations per second (combining read and write operations) for this disk from this server. |
Avg. Read Latency |
The original column name was Read Latency (ms) The average latency reported in milliseconds for read operations issued by the disk for the entire duration of the real-time collection from this server |
Avg. Write Latency |
The original column name was Write Latency (ms) The average latency reported in milliseconds for write operations issued by the disk for the entire duration of the real-time collection from this server |
Queue Depth |
The average queue depth for all IO to this hypervisor for the entire duration of the real-time collection from this server |
Read/Write Ratio |
The average read and write ratio as a percentage covering the time records when the IOPS for this disk were >= to the 90th percentile IOPS from this server Notes: This is not the average read/write ratio for the entire duration of the real-time collection. It is only the average for the top 10% of records by IOPS. In other words, when the disk was at it’s busiest, this is the read/write ratio. |
Vendor |
This value is only present if this disk is part of a VMware deployment. The disk vendor name |
Model |
This value is only present if this disk is part of a VMware deployment. The disk model name |
Lun Type |
This value is only present if this disk is part of a VMware deployment. One of these possible values: disk, tape, cdrom, communications, enclosure, mediaChanger, opticalDevice, printer, processor, scanner, storageArrayController, unknown, or worm |
SCSI Level |
This value is only present if this disk is part of a VMware deployment. The supported SCSI protocol level version for SCSI primary commands (an integer value ranging from 2 - 6) |
vStorageSupport |
This value is only present if this disk is part of a VMware deployment. vStorage hardware acceleration support status. If a storage device supports hardware acceleration, the ESXi host can offload specific virtual machine management operations to the storage device. With hardware assistance, the host performs storage operations faster and consumes less CPU, memory, and storage fabric bandwidth. |
Datacenter |
This value is only present if this disk is part of a VMware deployment. The name of the virtual datacenter that contains this ESXi host |
VMs Tab
Each row in this spreadsheet represents a guest virtual machine.
Field |
Description |
Guest VM Name |
The name of the virtual machine as assigned by the administrator in the hypervisor. Note: this is not always the same as the hostname |
Guest Hostname |
The hostname of the virtual machine if available |
IsRunning |
TRUE if the machine was running at the beginning of the Live Optics collection |
PowerState |
One of these values: poweredOn, poweredOff, or suspended This field might be empty for non-VMware hypervisor frameworks |
Guest VM OS |
The operating system of the guest VM as reported by the hypervisor framework |
VM Classification |
Either Standard or Outlier, this classification refers to the Provisioning chart shown in the Optical Prime online viewer Virtual Tab and the A.I.R. PPTX report. |
Virtual CPU |
The number of vCPUs that have been assigned to this guest virtual machine |
Provisioned Memory (Bytes) |
The provisioned memory for this virtual machine in bytes |
Used Memory (active) (Bytes) |
The memory currently in use by the virtual machine in bytes. The definition of active memory varies by hypervisor. The value shown is as observed during the discovery phase of collection. Notes: The discovery phase occurs at the beginning of a collection and the used memory reported here reflects that specific point in time. This value may differ with the peak and average memory values shown in the VM-Performance worksheet as those values are based on 24 hours of historical performance data. Active memory is an estimation calculated by the hypervisor of how much memory is currently being actively used by the guest virtual machine. We recommend that this active memory is used for sizing purposes. |
Consumed Memory (Bytes) |
This value is only present for VMware hypervisors. For non-VMware hypervisors, this value will always be zero. Amount of guest physical memory consumed by the virtual machine measured in megabytes as reported during the discovery phase of collection Notes: Consumed memory does not include overhead memory. It includes shared memory and memory that might be reserved, but not actually used. VMware recommends that this metric be used for charge-back purposes. We do not recommend that this memory be used for sizing purposes - use active memory instead. |
Guest VM Disk Capacity (MiB) |
The total capacity measured in megabytes of all drives on this guest virtual machine from the perspective of the guest operating system Notes: This value is reported by VMware Tools and will be unavailable if either VMware Tools is not installed or running properly. In the case where this value is not available, it will be a copy of the Virtual Disk Size (MB) data. |
Guest VM Disk Used (MiB) |
The used capacity measured in megabytes of all drives on this guest virtual machine from the perspective of the guest operating system Notes: This value is reported by VMware Tools and will be unavailable if either VMware Tools is not installed or running properly. In the case where this value is not available, it will be a copy of the Virtual Disk Used (MB) data. |
Guest VM % Occupancy |
|
Virtual Disk Size (MiB) |
The total size measured in megabytes of all virtual disks for this guest virtual machine from the perspective of the ESXi host |
Virtual Disk Used (MiB) |
The total used capacity measured in megabytes of all virtual disks for this guest virtual machine from the perspective of the ESXi host |
VMware Tools Version |
The version of VMware Tools installed on this guest virtual machine (if installed at all) Notes: If VMware Tools is not installed, this field will be blank. |
Connection State |
This value will only be present if the hypervisor is VMware. connected: vCenter has access to this guest virtual machine |
Template |
This value will only be present if the hypervisor is VMware. TRUE if this virtual machine is a template |
Unshared (MiB) |
This value will zero if the hypervisor is not VMware. |
Datacenter |
The name of the virtual datacenter that contains this guest virtual machine |
Cluster |
The name of the cluster that contains this guest virtual machine |
Hypervisor |
The name of the hypervisor that is hosting this guest virtual machine |
Guest IP1 |
The first IP address of this guest virtual machine |
Guest IP2 |
The second IP address of this guest virtual machine |
Guest IP3 |
The third IP address of this guest virtual machine |
Guest IP4 |
The fourth IP address of this guest virtual machine Notes: A guest virtual machine may be configured with any number of IP addresses, but only the first four are shown in this report |
Boot Time |
This value is only present if the hypervisor is VMware. |
Disks |
The number of virtual disks attached to this guest virtual machine |
NICs |
The number of virtual network interfaces attached to this virtual machine |
Custom Attributes Tab
Each row represents a custom attribute that is associated with a virtual machine. Only VMware hypervisors will report custom attributes.
Field |
Description |
Guest VM Name |
The name of the guest virtual machine that has this custom attribute |
Custom Attribute |
The name of this custom attribute |
Custom Content |
The value of this custom attribute |
Applications Tab
Each row in this worksheet represents an installed application.
Field |
Description |
Server Name |
The name of the server, desktop, or directly targeted virtual machine where this application is installed |
Software Title |
The name of the software package |
OS |
The operating system of the system |
Cloud Pricing Tab
This is based on Provisioned vCPU, Memory and Storage.
FIELD |
DESCRIPTION |
Data Center Name |
The VM Data Center name. If the server is not part of a cluster this field will be blank |
Machine name |
The DNS name of the server |
Instance UUID |
Shows UUID (Only supported for VMware Hypervisors) |
Virtual |
Boolean Flag indicating whether this is a Virtual or physical node |
Cores/vCPUs |
Total Virtual CPUs for the VM |
Memory (GiB) |
Total Memory allocated to the assessed Node |
Operating System |
Operating system of the assessed Node |
Storage (GiB) |
VM max capacity as provisioned by the VMware tools/OS |
Region |
AWS Server Region |
Retrieval Date (UTC) |
The date the pricing data was collected |
AWS Storage (GiB) |
The attached storage to the compute instance. |
AWS Storage Price/Month |
The attached storage price per month |
AWS On- Demand Pricing |
AWS on demand price in USD (Monthly aggregated) Note: this value includes the attached storage price per month |
AWS 1year Price |
AWS 1-year contract price in USD (Monthly aggregated). Note: this value includes the attached storage price per month |
AWS 3 years Price |
AWS 3-year contract price in USD (Monthly aggregated) Note: this value includes the attached storage price per month |
AWS Config Match |
Boolean flag indicating whether the on prem configuration was exactly matched with an AWS configuration or not |
AWS Matched instance |
Name of the instance to which the on Prem configuration matched |
AWS Notes |
An annex to the previous field indicating how your pricing was Matched for an AWS configuration and the instance name for direct and indirect match |
Google Cloud Storage (GiB) |
The attached storage to the compute instance. |
Google Cloud Storage Price/Month |
The attached storage price per month |
Google Cloud On- Demand Pricing |
Google Cloud on demand price in USD (Monthly aggregated) Note: this value includes the attached storage price per month |
Google Cloud 1year Price |
Google Cloud 1-year contract price in USD (Monthly aggregated) Note: this value includes the attached storage price per month |
Google Cloud 3 years Price |
Google Cloud 3-year contract price in USD (Monthly aggregated) Note: this value includes the attached storage price per month |
Google Cloud Config Match |
Boolean flag indicating whether the on prem configuration was exactly matched with a Google Cloud configuration or not |
Google Cloud Matched instance |
Name of the instance to which the on Prem configuration matched |
Google Cloud Notes |
An annex to the previous field indicating how your pricing was matched for a Google Cloud configuration and the instance name for direct and indirect match |
Azure Storage (GiB) |
The attached storage to the compute instance. |
Azure Storage Price/Month |
The attached storage price per month |
Azure On- Demand Pricing |
Azure on demand price in USD (Monthly aggregated) Note: this value includes the attached storage price per month |
Azure 1year Price |
Azure 1-year contract price in USD (Monthly aggregated) Note: this value includes the attached storage price per month |
Azure 3 years Price |
Azure 3-year contract price in USD (Monthly aggregated) Note: this value includes the attached storage price per month |
Azure Config Match |
Boolean flag indicating whether the on prem configuration was exactly matched with an Azure configuration or no |
Azure Matched instance |
Name of the instance to which the on Prem configuration matched |
Azure Notes |
An annex to the previous field indicating how your pricing was Matched for an Azure configuration and the instance name for direct and indirect match |
Cloud Pricing Peak Usage Tab
This is based on peak usage values for vCPU, Memory as well as the used Storage capacity.
FIELD |
DESCRIPTION |
Data Center Name |
The VM Data Center name. If the server is not part of a cluster this field will be blank |
Machine name |
The DNS name of the server |
Instance UUID |
Shows UUID (Only supported for VMware Hypervisors) |
Is Running |
If the Guest VM is Running or not |
Virtual |
Boolean Flag indicating whether this is a Virtual or physical node |
Peak vCPU% |
The maximum observed vCPU usage of this virtual machine based on 24 hours of historical data reported as a percentage. Note: The value ranges from 0 to 100%, but if the VM's upper vCPU limit is set to unlimited or a value higher than the provisioned/reserved vCPU, this value can exceed 100%. |
Peak vCPUs |
The Maximum number of vCPUs used observed for this virtual machine based on 1 hour of historical data. |
Peak Memory % |
The maximum active memory usage observed for this virtual machine based on 1 hour of historical data reported as a percentage of the memory provisioned for this virtual machine. |
Peak Memory (GiB) |
The maximum active memory usage observed for this virtual machine based on 1 hour of historical data reported in GiB |
Operating System |
Operating system of the assessed Node |
Used Storage (GiB) |
The reported VM Disk used capacity in GiB |
Region |
AWS Server Region |
Retrieval Date (UTC) |
The date the pricing data was collected |
AWS Storage (GiB) |
The attached used storage to the compute instance. |
AWS Storage Price/Month |
The attached used storage price per month |
AWS On- Demand Pricing |
AWS on demand price in USD based on Peak usage values (Monthly aggregated) Note: this value includes the attached storage price per month |
AWS 1year Price |
AWS 1-year contract price in USD based on peak usage values (Monthly aggregated). Note: this value includes the attached storage price per month |
AWS 3 years Price |
AWS 3-year contract price in USD based on peak usage values (Monthly aggregated) Note: this value includes the attached storage price per month |
AWS Config Match |
Boolean flag indicating whether the on prem configuration was exactly matched with an AWS configuration or not |
AWS Matched instance |
Name of the instance to which the on Prem peak usage values matched |
AWS Notes |
An annex to the previous field indicating how your pricing was Matched for an AWS configuration and the instance name for direct and indirect match |
Google Cloud Storage (GiB) |
The attached used storage to the compute instance. |
Google Cloud Storage Price/Month |
The attached used storage price per month |
Google Cloud On- Demand Pricing |
Google Cloud on demand price in USD based on Peak usage values (Monthly aggregated) Note: this value includes the attached storage price per month |
Google Cloud 1year Price |
Google Cloud 1-year contract price in USD based on Peak usage values (Monthly aggregated) Note: this value includes the attached storage price per month |
Google Cloud 3 years Price |
Google Cloud 3-year contract price in USD based on Peak usage values (Monthly aggregated) Note: this value includes the attached storage price per month |
Google Cloud Config Match |
Boolean flag indicating whether the on prem configuration was exactly matched with a Google Cloud configuration or not |
Google Cloud Matched instance |
Name of the instance to which the on Prem peak usage values matched |
Google Cloud Notes |
An annex to the previous field indicating how your pricing was matched for a Google Cloud configuration and the instance name for direct and indirect match |
Azure Storage (GiB) |
The attached used storage to the compute instance. |
Azure Storage Price/Month |
The attached used storage price per month |
Azure On- Demand Pricing |
Azure on demand price in USD based on peak usage values (Monthly aggregated) Note: this value includes the attached storage price per month |
Azure 1year Price |
Azure 1-year contract price in USD based on peak usage values (Monthly aggregated) Note: this value includes the attached storage price per month |
Azure 3 years Price |
Azure 3-year contract price in USD based on peak usage values (Monthly aggregated) Note: this value includes the attached storage price per month |
Azure Config Match |
Boolean flag indicating whether the on prem configuration was exactly matched with an Azure configuration or no |
Azure Matched instance |
Name of the instance to which the on Prem peak usage values matched |
Azure Notes |
An annex to the previous field indicating how your pricing was Matched for an Azure configuration and the instance name for direct and indirect match |