eG Help

In the Virtual Apps and Desktops environment, the Delivery Controller issues Power Management Actions such as TurnOn, TurnOff, Shutdown, Reset, Restart, Suspend, Resume, to the virtual machines. These power actions control the power states of the virtual machines at configurable times after session state changes, typically a set number of minutes after session disconnection or session logout. The power actions allow you to start, restart and stop certain machines during certain periods. For example, you may have a delivery group of desktops for users who work at normal business hours. After office hours, and as long as the user has been disconnected for a short period of time, the virtual machine could be powered off automatically. This helps you to plan resource allocations to the users according to their need and business policies, thus preventing resource wastage and saving cost. As the power actions play vital role in controlling power states of the virtual machines, it is important for administrators to track the successful completion of the actions at regular intervals. This is where the CtxXcXDPMgmtTest test helps!

With the help of this test, you can determine the number of power management actions that are started to be performed and the count of previous actions that are currently pending in the queue. This helps you find out the current load on the hypervisor and also prevent overloading condition. This test also reveals the count of the power actions that are in the same state for more than the configured time. Knowing the long running actions may help administrators to investigate the issues and fix them before they affect user experience. Details diagnosis provided by the test reveals the deep insights such as actions IDs, state of the actions, the hypervisor to which the actions are issued, etc.

Outputs of the test : One set of results for each delivery group that is configured with the Delivery Controller 7.

Measurement	Description	Measurement Unit	Interpretation
Started_actions	Indicates the number of power management actions that are started to be performed on the virtual machine.	Number	The detailed diagnosis of this measure revels the following details: The unique identifier of the power action that has been started. The name of the power action to be performed. The timestamp of when the action was created and placed in the queue. The fully qualified DNS name of the machine that the power action applies to. The name of the virtual machine that the power action applies to. The catalog to which the machine belongs to. The hypervisor's name for the machine that the power action applies to. The current state of the power action. The time when the power action was started to be processed by the hypervisor.
Pending_actions	Indicates the number of power management actions that are currently pending.	Number	The detailed diagnosis of this measure revels the following details: The unique identifier of the power action that are pending in the queue. The name of the power action to be performed. The timestamp of when the action was created and placed in the queue. The fully qualified DNS name of the machine that the power action applies to. The name of the virtual machine that the power action applies to. The catalog to which the machine belongs to. The hypervisor's name for the machine that the power action applies to. The current state of the power action. The time when the power action was started to be processed by the hypervisor.
Long_running_actions	Indicates the number of actions executing on the virtual machines that have been running for more time than the time specified against the Long running action in seconds parameter.	Number	The detailed diagnosis of this measure revels the following details: The unique identifier of the power action that has been started. The name of the power action to be performed. The timestamp of when the action was created and placed in the queue. The fully qualified DNS name of the machine that the power action applies to. The name of the virtual machine that the power action applies to. The catalog to which the machine belongs to. The hypervisor's name for the machine that the power action applies to. The current state of the power action. The time when the power action was started to be processed by the hypervisor.