Analyzing sole-tenant node usage

This document describes how you can analyze your usage of VM instances and sole-tenant nodes by using IAP Desktop.

Analyzing usage of VMs and sole-tenant nodes provides insights often required for effectively reporting your per-physical core based licenses (commonly applicable for Windows Server and MS SQL Server BYOL use cases). For these per-physical core based licenses, IAP Desktop provides you with granular metrics to aid in your reporting including:

  • Number of unique physical hosts used over a given period of time
  • Peak usage of physical hosts over a given period of time
  • Unique server identifiers for each host
  • Days each physical server was used
  • Lineage of physical servers used for each instance

Before you begin

Before you can use IAP Desktop to create a usage report, you must ensure that the following prerequisites are met:

  • You've downloaded and installed the latest version of IAP Desktop on your local computer and have signed in by using your Google identity.
  • You have Logs Viewer (or equivalent) access to the Google Cloud project that you plan to analyze.

Connecting IAP Desktop to your Google Cloud project

To connect IAP Desktop to your Google Cloud project, do the following:

  1. In IAP Desktop, select File > Add Google Cloud project.
  2. Enter the ID or name of your Google Cloud project and click OK.

Creating a usage report

You are now ready to create a usage report:

  1. In IAP Desktop, right-click the project that you want to analyze and select Report > New instance/node usage report.
  2. In the dialog, select the time frame that you want to analyze.
  3. Click OK to create the report.

To create the usage report, IAP Desktop analyzes the audit log data of your project. Depending on the volume of past activity in the project, the analysis might take between 1 and 5 minutes per month that needs to be analyzed.

Once the analysis is complete, IAP Desktop opens the report:


Exploring the usage report


The Instances tab shows how many VM instances were used over the analyzed time period. By default, the report includes all VM instances. Use the filter buttons in the toolbar to include or exclude VM instances by tenancy, operating system, or license.

The report only considers running instances and ignores VM instances while they are stopped. The list at the bottom of the report shows which VM instances were counted:

  • Instance ID is the unique ID of the VM instance.
  • Instance name, zone, and project ID identify the VM instance. Because an instance name can be reused after a VM instance has been deleted, you might see multiple VM instances with the same name but different IDs.
  • From and To indicate when the VM instance was started and when it was stopped. If a VM instance was started and stopped multiple times, the list includes multiple entries for the VM.

You can select a time range within the chart. The list of VM instances then updates to only show instances that were running during the selected time period.

Sole-tenant nodes

The Sole-tenant nodes tab shows how many sole-tenant nodes were used to run your VM instances. Instead of showing all your nodes, the report shows sole-tenant nodes that were hosting VM instances that match certain criteria. Use the filter buttons to select these criteria.

For example, if you set your filter criteria to only include Windows and Bring-your-own-license, then the report only shows sole-tenant nodes that were running at least one VM matching these criteria. Other sole-tenant nodes, like those exclusively running Linux VMs, are ignored.

The list below the chart shows details about the sole-tenant nodes:

  • Server ID is the unique ID of an incarnation of a sole-tenant node. Every time a sole-tenant node is taken down for maintenance and replaced, the node is assigned a new Server ID.
  • First use and Last use indicate the first time and the last time the node was used by a VM instance that matches your selected criteria.
  • Days used indicates for how many days the node was used by a VM instance that matches your selected criteria (difference between First use and Last use).
  • Peak VMs indicates the peak number of VM instances running in parallel matching your selected criteria.

You can use the mouse to select a time range within the chart. The list of sole-tenant nodes is then updated to only nodes that were used during the selected time period.

If you click one of the sole-tenant nodes, the list at the bottom updates to show the list of VM instances that ran on that particular node within the selected time period.


The Licenses tab shows the total number of physical CPU cores of the sole-tenant nodes that were used to run your Windows BYOL instances.

What's next