Filter data to troubleshoot failures

When you click numbers on the Dashboard or select a predefined filter from the Filters menu, the Filters view opens to display data based on the selected machine or failure type.

Predefined filters cannot be edited, but you can save a predefined filter as a custom filter and then modify it. Additionally, you can create custom filtered views of machines, connections, sessions, and application instances across all Delivery Groups.

  1. Select a view:

    • Machines. Select Single-session OS Machines or Multi-session OS Machines. These views show the number of configured machines. The Multi-session OS Machines tab also includes the load evaluator index, which indicates the distribution of performance counters and tool tips of the session count if you hover over the link.
    • Sessions. You can also see the session count from the Sessions view. Use the idle time measurements to identify sessions that are idle beyond a threshold time period.
    • Connections. Filter connections by different time periods, including last 60 minutes, last 24 hours, or last 7 days.
    • Application Instances. This view displays the properties of all application instances on VDAs of Server and Single-session OS. The session idle time measurements are available for Application instances on VDAs of Multi-session OS.

    Note:

    If you have launched Desktop sessions on VDAs installed on a Windows 10 1809 computer, the Activity Manager in Director might sometimes display Microsoft Edge and Office as actively running applications while they are actually running only in the background.

  2. For Filter by, select the criteria.
  3. Use the additional tabs for each view, as needed, to complete the filter.
  4. Select additional columns, as needed, to troubleshoot further.
  5. Save and name your filter.
  6. To access filters from multiple Director servers, store the filters on a shared folder accessible from those servers:
    • The shared folder must have modify permissions for accounts on the Director server.
    • The Director servers must be configured to access the shared folder. To do this, run IIS Manager. In Sites > Default Web Site > Director> Application Settings, modify the Service.UserSettingsPath setting to reflect the UNC path of the shared folder.
  7. To open the filter later, from the Filters menu, select the filter type (Machines, Sessions, Connections, or Application Instances), and then select the saved filter.
  8. Click Export to export the data to CSV format files. Data of up to 100,000 records can be exported. This feature is available in Delivery Controller(s) version 1808 and later.
  9. If needed, for Machines or Connections views, use power controls for all the machines you select in the filtered list. For the Sessions view, use the session controls or option to send messages.
  10. In the Machines and Connections views, click the Failure Reason of a failed machine or connection to get a detailed description of the failure and actions recommended to troubleshoot the failure. The failure reasons and the recommended actions for Machine and Connection failures are available in the Citrix Director 7.12 Failure Reasons Troubleshooting Guide.
  11. In the Machines view, click on a machine name link to go to the corresponding Machine Details page. This page displays the details of the machine, provides power controls, displays the CPU, memory, disk monitoring, and GPU monitoring graphs. Also, click View Historical Utilization to see the resource utilization trends for the machine. For more information, see Troubleshoot machines.
  12. In the Application Instances view, sort or filter based on Idle Time greater than a threshold time period. Select the idle application instances to end. Log off or Disconnect of an application instance ends all active application instances in the same session. For more information, see Troubleshoot applications. The Application Instances filter page and idle time measurements in the Sessions filter pages are available if Director, Delivery Controller(s), and VDAs are version 7.13 or later.

Note: Citrix Studio allows assignment of multiple Desktop Assignment Rules (DAR) for different users or user groups to a single VDA in the Delivery Group. StoreFront displays the assigned desktop with the corresponding Display Name as per the DAR for the logged in user. However, Director does not support DARs and displays the assigned desktop using the Delivery Group name regardless of the logged in user. As a result, you cannot map a specific desktop to a machine in Director. To map the assigned desktop displayed in StoreFront to the Delivery Group name displayed in Director, use the following PowerShell command:

Get-BrokerDesktopGroup | Where-Object { $\_.Uid -eq (Get-BrokerAssignmentPolicyRule | Where-Object { $\_.PublishedName -eq "\<Name on StoreFront\>" }).DesktopGroupUid } | Select-Object -Property Name, Uid
<!--NeedCopy-->
Filter data to troubleshoot failures

In this article