Column Descriptions of the Headers for GCP(IAAS)
GCP |
|
|---|---|
Summary Table |
|
Asset Group | Name of asset group. |
Server Name | The hostname or machine name of the server detected by the collector. |
IP Address | The primary internal IP address associated with the server. |
OS | The base operating system family (e.g., Windows, Linux). |
OS Version | The specific release or build of the operating system (e.g., Windows Server 2019, RHEL 8.6). |
Recommended Instance | The specific cloud VM size that Cloudamize suggests based on performance data. |
Recommended vCPU | The number of vCPUs required in the cloud to meet the workload's performance requirements. |
Recommended Storage Type | The specific cloud storage tier or disk type is suggested to match the IOPS and throughput requirements observed on the source server. |
MS SQL Edition | (If applicable) The detected edition of Microsoft SQL Server (e.g., Enterprise, Standard, Express). |
SQL Version | (If applicable) The version year or engine number of the SQL Server installation (e.g., SQL Server 2019). |
Total Cost ($) | The combined annual cost for the machine, including Compute, Storage, Network, and Licensing. |
Compute Cost ($) | The annual cost specifically for the cloud instance’s CPU and RAM. |
Network Cost ($) | The estimated annual cost for data egress and regional data transfer based on observed traffic patterns. |
Storage Cost ($) | The annual cost for cloud disks (EBS/Managed Disks) and provisioned performance (IOPS/Throughput). |
|
|
Compute Table |
|
Asset Group | A user-defined sub-grouping or application tag for organizing machines within a Group. |
Server Name | The hostname or machine identifier detected by the data collector. |
OS | The base operating system family (e.g., Windows, Linux). |
OS Version | The specific release or build of the operating system (e.g., Windows Server 2019, RHEL 8.6). |
Recommended Instance | The suggested cloud VM based on your performance and pricing plan. |
Constraint | Identifies the primary performance factor (e.g., CPU, RAM, or IOPS) that determined the recommended instance size. If a larger instance was chosen to satisfy a specific resource peak, it will be noted here. |
MS SQL Edition | (If applicable) The detected edition of Microsoft SQL Server (e.g., Enterprise, Standard, Express). |
SQL Version | (If applicable) The version year or engine number of the SQL Server installation (e.g., SQL Server 2019). |
On Time (%) | The percentage of time the physical machine was powered on during the collection period. |
Recommended Daily ON Time (%) | Machine on-time percentage of representative one day. In other words, it is daily on-time percentage. Each day’s on-time over all days during data collection is used to derive this daily (representative one day) on-time percentage. On-time percent from 0 to 24 hours. |
Recommended Weekly ON Time (%) | Machine on-time percentage of the representative week. In other words, it is the weekly on-time percentage. Each week’s on-time over all days during data collection is used to derive this weekly (representative one week) on-time percentage. On-time percent from Sunday to Saturday. |
Observed vCPU | The actual number of vCPUs/Cores present on the source server. |
Recommended vCPU | The number of vCPUs suggested in the cloud to support your performance targets. |
Current CPU Utilization (%) | The observed average CPU usage on the source server during the collection period. |
Predicted CPU Utilization (%) | The estimated CPU usage on the Recommended Instance based on its specific performance benchmarks. |
Max Allowed CPU Utilization (%) | The user-defined threshold (SLT) that Cloudamize uses to ensure the CPU is not over-provisioned. |
Observed Memory Provisioned (GB) | The total physical RAM currently installed on the source server. |
Peak Memory Used (GB) | The maximum amount of RAM utilized by the source server at any point during collection. |
Recommended Memory (GB) | The amount of RAM provisioned in the suggested cloud instance. |
Total Cost ($) | The combined annual cost (Compute, Storage, Network, and Licensing). |
Region | The target cloud region. |
Pricing Plan | Type of pricing plan from the IAAS provider. |
Network + Disk Egress Bandwidth |
|
Required (Gbps) | The measured amount of outbound data transfer speed (throughput) required by the source workload to function without performance degradation. |
Available (Gbps) | The maximum outbound throughput capacity provided by the Recommended Instance in the target cloud environment. |
Network + Disk Ingress Bandwidth |
|
Required (Gbps) | The measured amount of inbound data transfer speed (throughput) required by the source workload. |
Available (Gbps) | The maximum inbound throughput capacity provided by the Recommended Instance in the target cloud environment. |
Disk | |
Required Number of vCPUs for Disk IOPS | The specific count of virtual CPUs needed on the target instance is specifically to handle the Input/Output Operations Per Second (IOPS) generated by the workload's storage demands. |
Required Number of Disks | The number of distinct storage volumes required to support the data and performance needs of the source server. |
Available Number of Disks | The maximum number of storage volumes that the Recommended Instance type can support, according to the cloud provider’s limits. |
|
|
Storage Table |
|
Asset Group | A user-defined sub-group or application tag used to categorize a set of machines within a Group. |
Server Name | The hostname or identifier of the source machine as detected by the collection tool. |
Disk | The specific volume or partition identifier being analyzed (e.g., |
Observed Disk Capacity (GB) | The total physical storage space currently allocated to the disk on the source server. |
Observed Disk Occupancy (GB) | The actual amount of storage space currently utilized by data on the source disk. |
Recommended Storage Type | The suggested cloud storage tier based on performance needs. |
Recommended Storage Type | Recommended storage type. |
Size (GB) | The capacity of the cloud disk is recommended to support both data and performance requirements. |
Region | The target cloud data center location where the instance and storage costs are calculated. |
Annual Cost ($) | The projected yearly expenditure for this specific disk volume based on the selected pricing plan. |
Standard Disk Provisioning |
|
Size (GB) | The total storage capacity recommended for the cloud disk. This is calculated to ensure there is enough space for your current data (Occupancy) while also meeting the performance requirements of the selected storage tier. |
Annual Cost ($) | The projected yearly cost for this specific storage volume. This value is derived from the cloud provider's regional pricing for the recommended storage type and the provisioned size. |
Standard Disk IOPS | |
Required Read | The measured number of read operations per second performed by the workload on the source disk. |
Available Read | The maximum read IOPS capacity supported by the recommended cloud storage tier. |
Required Write | The measured number of write operations per second performed by the workload on the source disk. |
Available Write | The maximum write IOPS capacity supported by the recommended cloud storage tier. |
Standard Disk Bandwidth | |
Required Read (MBps) | The measured throughput (data transfer speed) required for read operations on the source disk, in Megabytes per second. |
Available Read (MBps) | The maximum read throughput supported by the recommended cloud storage tier. |
Required Write (MBps) | The measured throughput (data transfer speed) required for write operations on the source disk, in Megabytes per second. |
Available Write (MBps) | The maximum write throughput supported by the recommended cloud storage tier. |
Standard Disk Instance | |
IOPS Limit Utilization | A percentage value indicating how much of the recommended cloud instance's total IOPS capacity is being consumed by the workload's peak storage operations. A high percentage (near 100%) suggests the instance type itself, rather than just the disk, may be a performance bottleneck. |
Disk Bandwidth Limit Utilization | A percentage value indicating how much of the recommended cloud instance's total throughput (MBps) capacity is being consumed by the workload. This tracks the data transfer limit between the VM and its attached storage. |
SSD Provisioning | |
Size (GB) | The total storage capacity recommended for the SSD tier. This is calculated to ensure the disk is large enough to hold your data while providing the high-performance IOPS and throughput associated with SSD storage. |
Annual Cost ($) | The projected yearly cost for the recommended SSD volume. This is based on the cloud provider's regional pricing for the specific SSD tier (e.g., AWS gp3 or Azure Premium SSD) and the provisioned capacity. |
SSD IOPS |
|
Required Read | The measured peak number of read operations per second (IOPS) performed by the source workload on its Solid State Drive (SSD) storage. |
Available Read | The maximum read IOPS capacity supported by the recommended cloud SSD tier (e.g., AWS gp3 or Azure Premium SSD). |
Required Write | The measured peak number of write operations per second (IOPS) performed by the source workload on its SSD storage. |
Available Write | The maximum write IOPS capacity supported by the recommended cloud SSD tier. |
SSD Bandwidth | |
Required Read (MBps) | The measured maximum read throughput (data transfer speed) required by the workload on its SSD storage, measured in Megabytes per second. |
Available Read (MBps) | The maximum read throughput capacity supported by the recommended cloud SSD tier (e.g., AWS gp3 or Azure Premium SSD). |
Required Write (MBps) | The measured maximum write throughput (data transfer speed) required by the workload on its SSD storage, measured in Megabytes per second. |
Available Write (MBps) | The maximum write throughput capacity supported by the recommended cloud SSD tier. |
SSD Instance Limits | |
IOPS Limit Utilization | A percentage value indicating how much of the recommended cloud instance's total aggregate IOPS capacity is being consumed by the workload's peak SSD operations. This tracks the VM-level ceiling, which can be lower than the sum of individual disk limits. |
Disk Bandwidth Limit Utilization | A percentage value indicating how much of the recommended cloud instance's total available throughput (MBps) is being consumed by the workload. This monitors the data pipe between the VM and its attached SSD storage to ensure no throttling occurs at the instance level. |
Local SSD Provisioning | |
Size (GB) | The total storage capacity allocated to the Local (Ephemeral) SSD. Unlike persistent network storage, these are physically attached to the host server, providing ultra-low latency and high performance for temporary data, swap files, or NoSQL databases. |
Annual Cost ($) | The projected yearly cost for the Local SSD. For many cloud providers, this cost is bundled into the hourly price of the specific "L" or "d" series instance types, while for others (like GCP), it represents the specific surcharge for adding Local SSD partitions. |
Local SSD IOPS | |
Required IOPS | The measured total number of Input/Output Operations Per Second (read and write combined) that the source workload performs on its local/ephemeral SSD storage. |
Available IOPS | The maximum IOPS capacity provided by the physically attached Local SSD of the recommended cloud instance type (e.g., AWS i4i or Azure Lsv3 series). |
|
|
Network Table |
|
Asset Group | A user-defined sub-grouping or metadata tag used to further classify specific applications or service layers (e.g., "DB-Cluster-01") within a larger Group. |
Instance Type | |
Server Name | The specific hostname or machine label of the source server identified during the data collection process. |
IP Address | The primary network identifier (IPv4) used by the source server to communicate within your local or virtual network. |
Recommended Instance | The specific cloud virtual machine size suggested by Cloudamize to match the performance and cost requirements of the workload. |
Network Utilization | |
GB/month leaving server | The measured total volume of data (Egress) transmitted out of the source server to external networks or other cloud regions. |
GB/month from other Servers/Devices | The measured total volume of data (Ingress) received by the source server from the internet or other internal resources. |
Predicted Peak (%) | The estimated maximum network bandwidth utilization on the Recommended Instance is calculated by comparing your source peak traffic against the cloud instance's throughput limit. |
Annual Cost for Transmitted Data ($) | The projected yearly cost for outbound data transfer (Egress). This is based on cloud provider data transfer pricing for traffic leaving the region or moving to the internet. |
Annual Cost for Received Data ($) | The projected yearly cost for inbound data transfer. While most cloud providers do not charge for ingress, this identifies any costs associated with specialized services like Load Balancers or Inter-zone transfers. |
Annual cost($) |
|
Region | The geographic cloud data center location (e.g., |
Total Cost ($) | The cumulative annual expenditure for the entire server. This is the sum of all associated costs, including Compute, Storage, Network Egress, and any detected Software Licensing. |
Planner Icons |
|
|---|---|
Fit in Bounds | When “Fit In Bounds” is clicked, the entire graph in migration planner is nicely fit with centering. |
Zoom Out | Zoom out means to make the image look smaller for pinching out. |
Zoom In | Zoom in means focusing on a particular place on a image to increase its size or make the image look larger by pinching in |
Collapse all assets | It will collapse the modified/changed assets |
Clear All | It will clear any mapped dependencies |
Undo Migration Planner Changes | Will revert the changes made in Migration Planner |
Application Inventory Settings | By clicking Application Inventory Settings, it will allow us to select the applications that you want to migrate |
Build Application-Based Move Groups | Move groups can be built in multiple ways, by default Move groups are built on application categories, the Cloudamize Platform allows for the creation of new groups or assets by creating Application-Based Move Groups. To make adjustments, click on the More Tools button, and select Build-Application Based Move Groups |
Build Machine-Based Move Groups | In addition to Application-Based Move Groups, the Cloudamize Platform allows for the creation of Machine-Based Move Groups To make adjustments, click on the More Tools button, and select Build-Machine Based Move Groups. A new window will open with two sections, the bottom section lists all processes found during the assessment and the top section, is where we will be adding rules for these machines. |
Advanced Filtering | Advanced Filtering allows you to create move groups based on nearly any metric collected by the Cloudamize platform. |
Migrate Your environment | This Option allows us to know how to migrate a set of machines to respective IAAS using Application Migration Service (MGN). After an installation key has been provided, the MGN agent can be downloaded and installed from the Cloudamize application. Machines which are candidates for migration to AWS will then be available in the MGN dashboard. |
Upload File | An option to be used to upload a .CSV file |
CSV Builder | The Cloudamize CSV Builder allows you to create custom CSV outputs to provide you with the data which is most important to you. You can choose the categories to display as columns in the downloadable CSV output and you can reorder the columns to fit your needs. Select columns based on machine-centric data such as observed and recommended number of CPU threads, allocated memory, operating system, and many more and the templates can also be created based on application-centric data such as the application category, description, vendor, process, etc. |
CSV Exporter | This option lets you create a custom template by using an option of drop-down list to select a plan and to apply to the data in the selected templates |
SQL Server and License Usage | Using the Migration Planner, Cloudamize now provides a more in-depth look at the SQL Servers found in the assessed infrastructure. The information provided within the SQL Server and License Usage machine allows you to gain further insight into the on-premise licensing data and view a comparison of host-based versus VM-based SQL licensing. This feature also provides an overview of necessary on-cloud SQL licensing. |
Migration Planner Table | |
|---|---|
Number Of Nodes | The number of nodes in an asset. |
Number Of Communicating Apps | The number of communicating unique applications in an asset. This app can be a client or server app. |
Number Of Inter-Communicating Clients | The number of inter-communicating client nodes in other assets to a server node in this asset. Note that this is a node-level, not an app-level. This shows how many client nodes in other assets communicate to this asset. |
Number Of Inter-Communicating Servers | The number of inter-communicating server nodes in other assets from a client node in this asset. Note that this is a node-level, not an app-level. This shows how many server nodes in other assets are communicated by this asset. |
Number Of Proprietary Apps | The number of proprietary applications. Seems not supported |
Number Of Specialized Apps | The number of specialized applications. Seems not supported |
Number Of Autoscalable Nodes | The number of auto-scalable nodes where node does not run SQL server and the CPU utilization performance is suitable for auto-scaling. |
Number Of Nodes Suitable For GP-SSD | he number of nodes where disk IOPS performance are bursty and suitable for GP-SSD. |
Number Of Nodes Suitable For The t2 Family | The number of nodes where the recommended instance type is t2 family. |
Suitable Instance Types Are Available | The recommended instance type meets the performance requirement with CPU and memory workload. |
Migration Planner Table |
|
|---|---|
Number Of Nodes | The number of nodes in an asset. |
Number Of Communicating Apps | The number of communicating unique applications in an asset. This app can be a client or server app. |
Number Of Inter-Communicating Clients | The number of inter-communicating client nodes in other assets to a server node in this asset. Note that this is a node-level, not an app-level. This shows how many client nodes in other assets communicate to this asset. |
Number Of Inter-Communicating Servers | The number of inter-communicating server nodes in other assets from a client node in this asset. Note that this is a node-level, not an app-level. This shows how many server nodes in other assets are communicated by this asset. |
Number Of Proprietary Apps | The number of proprietary applications. Seems not supported |
Number Of Specialized Apps | The number of specialized applications. Seems not supported |
Number Of Autoscalable Nodes | The number of auto-scalable nodes where node does not run SQL server and the CPU utilization performance is suitable for auto-scaling. |
Number Of Nodes Suitable For GP-SSD | he number of nodes where disk IOPS performance are bursty and suitable for GP-SSD. |
Number Of Nodes Suitable For The t2 Family | The number of nodes where the recommended instance type is t2 family. |
Suitable Instance Types Are Available | The recommended instance type meets the performance requirement with CPU and memory workload. |