Auto-scale History for Host Pools

Auto-scale History for Host Pools

Warning: Nerdio Manager does not install the BgInfo Azure extension during any automation or management process. However, the BgInfo extension may be installed either through a scripted action directly, or unintentionally, as stated in the Azure PowerShell module issues report.

The auto-scale history visualization helps you understand auto-scale behavior and how it impacts your deployment.

The following are important auto-scale history features.

  • Time Range: At the top of the window, select the desired time range to display.

  • Show: At the top of the window, select the desired graph(s) to display.

  • Savings: At the top of the window, you can view auto-scale savings. Select view details to see the savings details.

  • Hover: You can hover over any part of any graph to see its details. For example:

  • At the bottom of any graph, select the data set name to toggle on/off the display line associated with that information. For example, select Peak capacity to suppress that line on the graph. Select it again to display it.

  • Depending on which auto-scale trigger has been configured, that determines which graph contains extra values. For example, if the auto-scale trigger is configured based on CPU Usage%, then the CPU Usage% graph contains extra data sets such as Scale In Threshold and Scale Out Threshold.

Note: Regardless of which auto-scale trigger is configured for the host pool, you can configure the host pool to always have the auto-scale process collect CPU, RAM, and Average active sessions data. See Auto-scale Settings for Host Pools for details. Otherwise, the auto-scale process only collects data related to the auto-scale trigger.

To view auto-scale history for a host pool:

  1. At the Account level, locate the host pool you want to work with.

  2. From the action menu, select Auto-scaleHistory.

  3. Select the desired time range and the specific graphs to display.

    • Active hosts: The Active hosts graph displays Section 1 of the auto-scale configuration (Host Pool Sizing) and host pool activity as recorded by the auto-scale process. This includes the following:

      • Base capacity: This is the number of session host VMs to always be part of this host pool. These session hosts may be stopped or running.

      • Min active capacity: This is the minimum number of running session hosts that are always available.

      • Burst capacity: This is the capacity to burst above the base capacity of session host VMs when there is user demand. The system automatically creates up to this number of new session host VMs above the base capacity when needed.

      • Active hosts: The current number of active session hosts at this point in time.

      • Peak capacity: This the highest number of recorded session hosts for this time period.

      Notes:

      • Select an action point to see its details in the Related Tasks section at the bottom of the window. In addition, for any task shown in Related Tasks, select Details to view the task's details.

      • Select any point on the graph to see the status of the session hosts in the Hosts Snapshot section at the bottom of the window.

    • CPU usage %: The CPU usage graph displays the CPU%.

    • User sessions: The User sessions graph displays the following information about when users are signing in and signing out. This includes users connected to full desktop sessions or RemoteApps.

      • Total user sessions: The total number user sessions, which includes disconnected sessions.

      • Active user sessions: The total number of active user sessions, which only includes users who are actively connected.

    • Savings %: The Savings graph displays compute and storage savings.

      Note: As session hosts are started or created, the savings goes down due to increased compute and storage resources. As session hosts are shut down, removed, or disk types converted, the savings go up.

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request

Comments (0 comments)

Article is closed for comments.