Troubleshoot applications
Application Analytics
TheApplicationsview displays application-based analytics in a single, consolidated view to help analyze and manage application performance efficiently. You can gain valuable insight into the health and usage information of all applications published on the site. The default view helps identify the top running applications. This feature requires VDAs Version 7.15 or later.
TheProbe Resultcolumn displays the result of application probing run in the last 24 hours. Click the probe result link to see more details in theTrends>Probe Resultspage. For more details on how to configure application probes, seeApplication and Desktop Probing.
TheInstancescolumn displays usage of the applications. It indicates the number of application instances currently running (both connected and disconnected instances). To troubleshoot further, click theInstancesfield to see the correspondingApplication Instancesfilters page. Here, you can select application instances to log off or disconnect.
Note:
For custom scope administrators, Monitor does not display application instances created under application groups. To view all application instances, you must be a full administrator. For more information, see Knowledge Center articleCTX256001.
Monitor the health of published applications in your site with theApplication Faultsand theApplication Errors列。这些列显示聚合麻木er of faults and errors that have occurred while launching the corresponding application in the last one hour. Click theApplication FaultsorApplication Errorsfield to see failure details on theTrends>Application Failurespage corresponding to the selected application.
The application failure policy settings govern the availability and display of faults and errors. For more information about the policies and how to modify them, seePolicies for application failure monitoringin Monitoring policy settings.
Real-time application monitoring
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 Citrix Virtual Apps and Desktops environment, to reconfigure poorly performing servers, or to maintain and upgrade applications.
TheApplication Instancesfilter page lists all application instances on VDAs of Multi-session and Single session OS. The associated idle time measurements are displayed for application instances on VDAs of Multi-session 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, selectFilters > Application Instancesand select a pre-saved filter or chooseAll Application Instancesand create your own filter.
An example of a filter would be as follows. AsFilter bycriteria, choosePublished Name(of the application) andIdle Time. Then, setIdle Timetogreater than or equal to一个特定时间限制并保存为reus过滤器e. From the filtered list, select the application instances. Select option to send messages or from theSession Controldrop-down, chooseLogofforDisconnectto end the instances.
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 theSessionsfilter page using the session state and the session idle time metric. Sort by theIdle Timecolumn or define a filter to identify sessions that are idle beyond a specific time limit. Idle time is listed for sessions on VDAs of Multi-session OS that have been idle for at least 10 minutes.
TheIdle timeis displayed asN/Awhen the session or application instance
- has not been idle for more than 10 minutes,
- is launched on a VDA of Single session OS, or
- is launched on a VDA running Version 7.12 or earlier.
Historical application failure monitoring
TheTrends->Application Failurestab displays failures associated with the published applications on the VDAs.
For more information about the availability of the application failure trends, seeData granularity and retentionarticle. The application failures that are logged to the Event Viewer with source “Application Errors” are monitored. ClickExportto generate reports in CSV, Excel, or PDF formats
The failures are displayed asApplication FaultsorApplication Errorsbased on their severity. The Application Faults tab displays failures associated with loss of functionality or data. Application Errors indicate problems that are not immediately relevant; they signify conditions that might cause future problems.
You can filter the failures based onPublished Application Name,Process NameorDelivery Group,andTime Period.The table displays the fault or error code and a brief description of the failure. The detailed failure description is displayed as a tooltip.
Note:
The Published Application name is displayed as “Unknown” when the corresponding application name cannot be derived. This typically occurs when a launched application fails in a desktop session or when it fails due to an unhandled exception caused by a dependent executable.
By default, only faults of applications hosted on Multi-session OS VDAs are monitored. You can modify the monitoring settings through the Monitoring Group Policies: Enable monitoring of application failures, Enable monitoring of application failures on Single session OS VDAs, and List of applications excluded from failure monitoring. For more information, seePolicies for application failure monitoringin Monitoring policy settings.
TheTrends> Application Probe Resultspage displays the results of application probing executed in the site for the last 24 hours and 7 days. For more details on how to configure application probes, seeApplication Probing.