Site Analytics 编辑

With full administrator permission, when you open Director, the Dashboard provides a centralized location to monitor the health and usage of a site.

Director dashboard

If there are currently no failures and no failures have occurred in the past 60 minutes, the panels stay collapsed. When there are failures, the specific failure panel automatically appears.

Note:

Depending on your organization’s license and your Administrator privileges, some options or features might not be available.

Panels on the Director Dashboard

User Connection Failures

Connection failures over the last 60 minutes. Click the categories next to the total number to view metrics for that type of failure. In the adjacent table that number is broken out by delivery groups. Connection failures include failures caused by application limits being reached. For more information on application limits, see Applications.

Failed Single-session OS Machines or Failed Multi-session OS Machines

Total failures in the last 60 minutes broken out by delivery groups. Failures broken out by types, including failed to start, stuck on boot, and unregistered. For Multi-session OS machines, failures also include machines reaching maximum load.

Licensing Status

License Server alerts display alerts sent by the License Server and the actions required to resolve the alerts. Requires License Server Version 11.12.1 or later. Delivery Controller alerts display the details of the licensing state as seen by the Controller and are sent by the Controller. Requires Controller for XenApp 7.6 or XenDesktop 7.6 or later. You can set the threshold for alerts in Studio. Licensing status displayed in Delivery Controllers > Details > Product Editions > PLT indicates Premium and not Platinum.

Grace State

Director displays one of the following grace states. This information is fetched from the Delivery Controller.

  1. Not Active: Not in any type of grace period. Normal licensing limits apply.

  2. Out of Box Grace: 10 connections for the first 30 days after a new installation when pointing to a license server with no licenses.

  3. Supplemental Grace: When all licenses are consumed, a 15 day grace period is provided for business continuity until new licenses are added, or consumption is reduced. Unlimited connections are allowed during the supplemental grace period. Users are not affected. Warnings shown in Director cannot be dismissed until the supplemental grace period expires or is reset.

  4. Emergency Grace: Comes into effect when the license server is unreachable or the license information cannot be fetched while brokering a connection. Emergency grace is valid for 30 days. Users are not affected. Errors shown in Director cannot be dismissed until the license server is reachable.

  5. Grace Expired: Emergency Grace or the supplemental grace period has expired.

For more information, see License overdraft and Supplemental grace period.

Sessions Connected

Connected sessions across all delivery groups for the last 60 minutes.

Average Logon Duration

Logon data for the last 60 minutes. The large number on the left is the average logon duration across the hour. Logon data for VDAs earlier than XenDesktop 7.0 is not included in this average. For more information, see Diagnose user logon issues.

Infrastructure

Lists your site’s infrastructure - hosts and Controllers. For infrastructure from Citrix Hypervisor or VMware, you can view performance alerts. For example, you can configure XenCenter to generate performance alerts when CPU, network I/O, or disk I/O usage go over a specified threshold on a managed server or virtual machine. By default, the alert repeat interval is 60 minutes, but you can configure this as well. For details, see the XenCenter Performance Alerts section in the Citrix Hypervisor product documentation.

Note:

If no icon appears for a particular metric, this indicates that this metric is not supported by the type of host you are using. For example, no health information is available for System Center Virtual Machine Manager (SCVMM) hosts, AWS and CloudStack.

Continue to troubleshoot issues using these options (which are documented in the following sections):

Monitor sessions

If a session becomes disconnected, it is still active and its applications continue to run, but the user device is no longer communicating with the server.

ActionDescription
View a user’s currently connected machine or sessionFrom the Activity Manager and User Details views, view the user’s currently connected machine or session and a list of all machines and sessions to which this user has access. To access this list, click the session switcher icon in the user title bar. For more information, see Restore sessions.
View the total number of connected sessions across all delivery groupsFrom the Dashboard, in the Sessions Connected pane, view the total number of connected sessions across all delivery groups for the last 60 minutes. Then click the large total number, which opens the Filters view, where you can display graphical session data based on selected delivery groups and ranges and usage across delivery groups.
End idle sessionsThe Sessions Filters view displays data related to all active sessions. Filter the sessions based on Associated User, delivery group, Session State, and Idle Time greater than a threshold time period. From the filtered list, select sessions to log off or disconnect. For more information, see Troubleshoot applications.
View data over a longer period of timeOn the Trends view, select the Sessions tab to drill down to more specific usage data for connected and disconnected sessions over a longer period of time (that is, session totals from earlier than the last 60 minutes). To view this information, click View historical trends.

Note:

If the user device is running a legacy Virtual Delivery Agent (VDA), such as a VDA earlier than version 7, or a Linux VDA, Director cannot display complete information about the session. Instead, it displays a message that the information is not available.

Desktop Assignment Rules limitation: 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. You can map the assigned desktop displayed in StoreFront to the delivery group name displayed in Director using 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

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据

词条统计

浏览:83 次

字数:9316

最后编辑:7年前

编辑次数:0 次

    我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
    原文