Q: What do I need to collect data from a Hyper-V host?
A: Install the Cloudamize Windows agent on your Hyper-V host machine (i.e., on the hypervisor) only. This allows Cloudamize to get basic inventory and performance-related data.
Q: Do I need to install agents on individual VMs?
A: For Cloudamize to collect application-level data, including application dependencies, you will need to install agents on individual VMs, or configure the Cloudamize Agentless Data Collector. This information is used to build move groups in the Migration Planner.
Q: What is the performance overhead of running agents on a Hyper-V host?
A: The Cloudamize agents are lightweight. Typically, they take less than 0.5% CPU utilization. Cloudamize Agents are Smart Agents. They run two processes. One is the data-collection agent, and the other is the watchdog agent. The watchdog agent monitors the data-collection agent and makes sure the data-collection agent is behaving correctly. The watchdog agent monitors every system metric and caps the data-collection agent if it goes beyond expected consumption. If any of the metrics is higher than the cap, then the data-collection agent sleeps and waits until it can start collecting again. For example, typically, our agents take less than 0.5% CPU utilization. However, if CPU utilization goes higher than 2%, data-collection agents sleep and wait for watchdog agents to tell them when to start collection again.
Q: When Cloudamize is assessing locally attached storage for each VM, is the Cloudamize agent able to distinguish between locally attached block storage and network-attached block storage (for example, in-guest iSCSI LUNs)? Or does it simply take all block storage attached to a VM?
A: Currently, the Windows Agent only collects any logical disk drives that appear in the "Logical Disk" performance category in Windows. Network Attached Storage isn’t included directly. The same is also true for Linux Agent as well (anything registered as a logical drive is included; NAS is not queried directly), so anything that falls under a logical drive is included in the results. Since we do not collect from NAS directly, we don’t currently distinguish in the results screens.
Q: Will configuring Cloudamize to collect data from VMware and Hyper-V also collect application dependency data?
A. Configuring Cloudamize to collect data from VMware and Hyper-V will only collect system-level data (CPU, memory, storage, network) as reported by the hypervisor (Hyper-V or VMware).
Data collected using the Agent or Agentless Data Collector methods is capable of capturing application-level data and dependency data(application interconnectivity, firewall rules, IP and DNS info, installed applications, etc.).
Q: Do we support analysing data on a Hyper-V cluster?
A. Our Windows Agent (WA) will work on a Hyper-V machine, but its functionality within a Hyper-V cluster might encounter certain uncertainties. For instance, while WA may successfully identify all virtual machines within the Hyper-V cluster through a single Hyper-V machine, it could encounter difficulties in obtaining resource performance data for some VMs. This could occur if WA fails to access resource performance on certain Hyper-V machines within the same cluster. Here are the proposed options to address this:
Option 1: Install the agent on each virtual machine individually.
Option 2: Install an ADC (Agent Data Collector) and add the virtual machines to it.
Option 3: Install the agent on each virtual machine and deploy WA on all Hyper-V machines within the cluster. This approach is typical in scenarios where a Hyper-V cluster is not utilized
If you have any queries, please get in touch with the helpdesk via our Helpdesk Portal or by email at helpdesk@cloudamize.com.