HealthCheck for Azure Plan Glossary
- Number of Groups: These are the number of groups that have been observed in your infrastructure. These groups are created on the Topology viewer. The machines in your infrastructure are classified into assets, and assets in turn form groups. Assets can contain multiple nodes.
- Number of Nodes: These are the number of nodes on which HealthCheck for Azure Agents are installed. This is different from the number of machines under HealthCheck for Azure assessment. For HealthCheck for Azure assessment of virtual machines, information is gathered from the vCenter and does not require installing HealthCheck for Azure Agents, but Migration Plan requires you to install HealthCheck for Azure Agents on virtual machines as well. For physical machines, HealthCheck for Azure Agents are required for both Assessment and Migration Plan.
- Estimated Client Nodes without HealthCheck for Azure Agents: Estimated client nodes on your network which do not have HealthCheck for Azure Agents installed. HealthCheck for Azure analyzes your network data and detects connections made to machines with agents from machines without agents and counts those. These do not include machines which may be external to your network.
- Number of Applications: These are the estimated unique number of applications in your infrastructure. The total number of applications per group and asset may not add up because this consolidation is done only at the infrastructure level. For example, if the service Tomcat runs on 10 different machines, it may be shown as 10 at asset/group level but is counted only once at the infrastructure level.
- Total cost: This is the estimated annual cost of running your infrastructure with mapping of equivalent IaaS instance settings using different mappings techniques and pricing plans. See HealthCheck for Azure plans for more details.
Cloud Suitability: This is a unit that reflects the ease of migration of your infrastructure to the cloud. We assess your workload model to capture many issues that affect the ease of migration.
Bursty applications are more cloud suitable
- Bursty IOPS and CPU
- Bursty CPU for database does not add to burstiness since databases are difficult to dynamically scale
- Need to have suitable instance types for the workload.
- Cloud Readiness: This is a unit that reflects the ease of migration of your infrastructure to the cloud. We assess your workload type and the application interconnectivity to determine this. For example, well-known/standard applications increase readiness as compared to proprietary applications. Groups that have many applications that communicate to other groups are less ready than groups that have fewer applications that communicate with machines in other groups. This principle applies to assets as well as individual machines.
- Well-known (e.g., Microsoft Exchange) applications increase readiness.
- Proprietary applications reduce readiness.
- Groups with many applications that communicate to other groups are less ready than groups with fewer applications that communicate with machines in other groups.
- Assets with many applications that communicate to other assets in the same group are less ready than groups with fewer applications that communicate with machines in other groups. However, communicating within a group does not impact readiness as much as communication between groups.
- Machines that have applications that communicate to applications in other machines in the same asset are less ready than those with only small number of communicating applications. However, communication within an asset does not impact readiness as much as communication between assets.