You can troubleshoot applications and sessions by using the idle time metric to identify instances that are idle beyond a specific time limit.
Typical use cases for application-based troubleshooting are in the healthcare sector, where employees share application licenses. There, you must end idle sessions and application instances to purge the XenApp and XenDesktop environment, to reconfigure poorly performing servers, or to maintain and upgrade applications.
The Application Instances filter page lists all application instances on VDAs of Server and Desktop OS. The associated idle time measurements are displayed for application instances on VDAs of Server OS that have been idle for at least 10 minutes.
Note: The Application Instances metrics are available on Sites of all license editions.
Use this information to identify the application instances that are idle beyond a specific time period and log off or disconnect them as appropriate. To do this, select Filters > Application Instances and select a pre-saved filter or choose All Application Instances and create your own filter.
An example of a filter would be as follows. As Filter by criteria, choose Published Name (of the application) and Idle Time. Then, set Idle Time to greater than or equal to a specific time limit and save the filter for reuse. From the filtered list, select the application instances you want to end. From the Session Control drop-down, choose Logoff or Disconnect.
Note: Logging off or disconnecting an application instance logs off or disconnects the current session, thereby ending all application instances that belong to the same session.
You can identify idle sessions from the Sessions filter page using the session state and the session idle time metric. Sort by the Idle Time column or define a filter to identify sessions that are idle beyond a specific time limit. Idle time is listed for sessions on VDAs of Server OS that have been idle for at least 10 minutes.
The Idle time is displayed as N/A when the session or application instance