OneIQ Pulse is a unified agent-less data collector that supports various platforms. This article explains how to collect inventory and performance data from Azure Stack HCI, Microsoft Failover Clusters and Standalone hosts with Hyper-V and the Virtual Machines running on them, including their CSV (Cluster Shared Volumes).

Discovering endpoints

  1. Choose Microsoft Failover Cluster option in "Select Discovery Target" menu

2. Enter hostname, username and password for the Microsoft Failover Cluster endpoint

Viewing discovered endpoints

Upon successful discovery, a new endpoint tile will appear in the Dashboard screen and display the IP address, credentials used and the current endpoint status.

OneIQ Pulse does not display tiles for individual virtual machines or other managed resources. This detailed information is only available in the OneIQ Portal.

Microsoft Failover Cluster running Hyper-V is discovered via its cluster FQDN, or cluster virtual IP (VIP).

Endpoint Lifecycle


When the Create button is clicked, OneIQ Pulse will attempt to discover the specified hostname or IP address and check if the Microsoft Failover Cluster responds. The discovery process typically takes less than 10 minutes. During this time, OneIQ Pulse connects to the Microsoft Failover Cluster and attempts to login and identify the target endpoint.


If the endpoint is successfully discovered, OneIQ Pulse will

  • Set its status to Detected and

  • Automatically schedule inventory and performance data collection tasks


After a baseline of inventory and performance data is collected, OneIQ Pulse will switch the endpoint status to Collecting and continue gathering

  • Performance data every 5 minutes

  • Inventory data every 1 hour

Each operation usually takes less than minute, but may take longer in larger environments.

Best Practice: Check data collection after 3-4 hours to ensure that all endpoints are still being successfully monitored.


  • How do I check the name of the target Microsoft Failover Cluster?

    • Login on any of the cluster nodes and run "Get-Cluster" in PowerShell:

Did this answer your question?