• No se han encontrado resultados

Capítulo 2: El rol de la democracia en el desarrollo

2.3 Libertad de empresas

A tier is a specific point where DC RUM collects performance data. It is a logical application layer, a representation of a fragment of your monitored environment.

If you use presentation servers (such as Citrix or Windows Terminal Services) and you have configured software services based on the ICA analyzer, the Citrix/WTS (presentation) tier will automatically be displayed in the Network Tiers section of the Tiers report.

The Citrix/WTS (presentation) tier belongs to the Network Tiers section because it is treated as an application delivery channel. For Citrix and Windows Terminal Services, the key metrics are network performance, server RTT, or server loss rate; not operations or operation time as it is for data center tiers.

This tier presents traffic related to the ICA analyzer for real users only.

Drilldown Reports from Tier Name

Click the Citrix/WTS (presentation) tier name to drill down to the Citrix Landing Page report, which shows general, network-related metrics for ICA-based software services. For more information, see Citrix Landing Page Report [p. 115].

Citrix Landing Page Report

The Citrix Landing Page report lists all software services based on the ICA analyzer.

How to Access the Report

To access this report:

Select Reports RUM Analysis Citrix Landing Page

Select Reports RUM Analysis Software Services and click the Citrix Landing Page tab.

Select Reports EUE Overview Tiers and click the Citrix/WTS (presentation) tier.

NOTE

Always start any Citrix analysis from the Citrix Landing Page, not from the Software Services report.

The general Application performance and Unique and affected users (performance) on the Software Services report do not fit the Citrix transaction model.

The Citrix Landing Page presents the KPIs that are specific to Citrix: Server realized bandwidth, Network performance, and Unique and affected users (network).

Report Contents and Usage

The Citrix Landing Page report is an access point from which you are able to analyze usage and performance of the Citrix infrastructure when delivering applications to end users. Use the drilldown available in Citrix reports to perform the fault domain isolation and answer the questions on the performance of your environment.

The Citrix Landing Page report offers tabs for quick access to related reports:Software Services (default tab for the Citrix Landing Page report)Servers

For more information, see Citrix Servers Report [p. 118]. • Published Applications

For more information, see Citrix Published Applications Report in the Data Center Real User Monitoring Citrix/Windows Terminal Services Monitoring User Guide.

Channels

For more information, see Citrix Channels Report in the Data Center Real User Monitoring Citrix/Windows Terminal Services Monitoring User Guide.

Sites

For more information, see Citrix Sites Report [p. 118].

Citrix measurements

The Citrix reports provide the measurements of the following categories: Performance

AMD monitors performance of each network session between end-users in remote locations and the datacenter where Citrix servers reside. These performance measurements reflect all key aspects of network connectivity required for smooth delivery of applications over Citrix.

Network performance

Network round-trip time and retransmission rate in the Network performance column.

Bandwidth

Total bandwidth usage broken into client and server. Server realized bandwidth

Effective network throughput experienced by the end users in the Server realized bandwidth column.

The Realized Bandwidth measurements are performed individually for each user and server. Realized bandwidth reflects actual network throughput during delivery of screen updates to the end user and user action data to the server. Realized bandwidth reflects the end-to-end quality perceived by the users of Citrix-delivered application. The reported realized bandwidth value triggers a state: 0-28 kbps, 28-128 kbps, >128 kbps. It is based on the Citrix provided rule-of thumb network bandwidth requirements for smooth XenApp/XenDesktop application delivery. Citrix recommends that the network designed to deliver applications with ICA should offer at least 28 kbps throughput. and 128 kbps is a safer assumption regarding ICA requirements.

Unique and affected users

ICA decode recognizes Citrix login names, enabling presentation of the

Client-datacenter connection quality measurements in context of the Citrix users. The reports display the number of unique users with the breakdown into how many were affected by network related problems and how many were not. The user columns allow you to drill down to other user related reports for detailed analysis.

Availability

The reports provide the number of TCP errors along with the availability ratio, which may indicate the cause of your server problems

Citrix Statistics

Additional information on resources utilization statistics of Citrix/WTS server is collected by the TCAM agent. The information includes CPU and memory load of the server and number of active terminal sessions.

Channels and published applications

Performance of the network link between end-user's display and the XenApp/XenDesktop server is analyzed individually for each published application and ICA channel. DC RUM reports on traffic breakdown between interactive screen updates, audio/video media, print and USB access, enabling fault domain isolation for performance problems perceived by the end users as "application slowness". Published Citrix application names are reported together with channel names, adding further precision to the fault domain isolation input data. For more information, see Citrix Channels Report in the Data Center Real User Monitoring Citrix/Windows Terminal Services Monitoring User Guide and Citrix Published Applications Report in the Data Center Real User Monitoring Citrix/Windows Terminal Services Monitoring User Guide.

Commands and command delivery time

For ICA channels, the AMD measures commands, and where possible operations. The difference between a command and an operation is that a command is a single-direction transmission of data, while operation has the request-response nature. The number of commands represents the number of ICA data transfers issued by server or client. Command might reflect a request to update client's screen (sent by server to client) or sending a keyboard event (sent by client to server); send a piece of document to print.. However, commands do not have a server response time - they are sent by ICA client or server and the other part receives them and processes them asynchronously. Therefore, the command delivery time for ICA channels represents time taken to transmit a command to the other side of the network link, not actual time to execute it there.

The request-response type of actions, such as screen launch or logon, can be measured as operations. In this case, the Citrix reports provide the operation related measurements with breakdown into slow and fast operations.

For more information, see Citrix Channels Report in the Data Center Real User Monitoring Citrix/Windows Terminal Services Monitoring User Guide and Citrix Published

Applications Report in the Data Center Real User Monitoring Citrix/Windows Terminal Services Monitoring User Guide.

Autodiscovery and Citrix

Until an autodiscovered software service is manually configured, it uses a generic decode, which for certain types of traffic (such as FTP) may make Application Performance values less precise.

For Citrix traffic, you should refer to the Citrix Landing Page report.

Drilldown reports

Click a software service name to drill down to a report listing all servers for this software service. For more information, see Citrix Servers Report [p. 118].

You can also access the Metric Charts reports from the software service name column.

You can also drill down to user related reports from the Unique and affected users (Network) column. For more information, see All Users Report [p. 161], Network Performance Affected Users Report [p. 162], and Availability Affected Users Report [p. 163].

Citrix Servers Report

The Citrix Servers report shows either all presentation servers that belong to the Citrix/WTS (presentation) tier or all servers on which the specific software service is offered.

How to Access the Report

To access this report, click a software service name on the Citrix Landing Page report.

Report Contents and Usage

This report shows detailed measurements for each presentation server, so you can see the number of bytes sent by a specific server and its availability. The set of default metrics is similar to the one of the Citrix Landing Page Report [p. 115] report, however it's supplemented with the Command breakdown and Command delivery time.

Drilldown Reports

Click the server IP address to drill down to a report showing metric charts for this server. For more information, see Metric Charts [p. 159].

Citrix Sites Report

The Citrix Sites report lists all client sites in which ICA-based traffic was detected during the selected period of time.

How to Access the Report

To access this report, click the Citrix/WTS (presentation) tier on the Tiers report, and then click the Sites tab.

Report Contents and Usage

This report helps you identify sites in which performance problems occur and analyze how they affect the users. The set of default metrics in the Usage, Performance, and Availability sections of the table is the same as on the Citrix Landing Page report. For more information, see Citrix Landing Page Report [p. 115].

Drilldown Reports

You can access more detailed reports from the following columns: • Client site

Metric Charts report.

For more information, see Metric Charts [p. 159]. • Unique and affected users (network)

All Users report.

For more information, see All Users Report [p. 161]. ◦ Network Performance Affected Users report.

For more information, see Network Performance Affected Users Report [p. 162]. ◦ Availability Affected Users report.

For more information, see Availability Affected Users Report [p. 163].