EdgeSight User Guide

Citrix EdgeSight Users Guide
Citrix EdgeSight for Presentation Server 4.5 Citrix EdgeSight for Endpoints 4.5
Copyright and Trademark Notice Use of the product documented in this guide is subject to your prior acceptance of the End User License Agreement. A printable copy of the End User License Agreement is included on your product CD-ROM. Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Citrix Systems, Inc. 2007 Citrix Systems, Inc. All rights reserved. Citrix is a registered trademark, and Citrix Presentation Server and EdgeSight are trademarks of Citrix Systems, Inc. in the United States and other countries. Trademark Acknowledgements
Adobe, Acrobat, and Flash are trademarks or registered trademarks of Adobe Systems Incorporated in the U.S. and/or other countries.
Microsoft, Windows, Windows Server, and Internet Explorer are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks and registered trademarks are the property of their respective owners. Document Code: June 7, 2007 (MS)
C ONTENTS
Contents
Chapter 1
Overview
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 Implementing Solutions with EdgeSight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 Resolve System Performance Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 Resolve Application Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 Resolve Network Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 Proactively Manage Hardware and Software Assets . . . . . . . . . . . . . . . . . . . . . .9 Capture and Store Data for Long Term Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Chapter 2
Using Citrix EdgeSight Reports

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 Citrix EdgeSight Server Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 Accessing and Using Historical Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 Finding Reports Using the Support Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 Finding Related Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 Accessing and Using Remote Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 Using Real-Time Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 Real-Time Report Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 Displaying Real-Time Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 Customizing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 Accessing and Using Real Time Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Accessing and Using Process Fault Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Capturing Context at the Onset of a Performance Problem . . . . . . . . . . . . . . . .21
Chapter 3
Using EdgeSight to Resolve System Performance Problems

System Performance Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 Displaying Recent Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Displaying the Historical Performance for a Device . . . . . . . . . . . . . . . . . . . . . . . .25 Display Asset Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 Display Resource Utilization Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Chapter 4
Using EdgeSight to Resolve Session Performance Problems

Session Performance Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Displaying Session Latency Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 Displaying Round Trip Time Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 Displaying Client and Server Session Startup Time Data . . . . . . . . . . . . . . . . . . . .29 Displaying Real Time Session Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . .30
Chapter 5
Using Citrix EdgeSight to Resolve Applications Problems

Application Problem Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 Problem Notification and Initial Investigation. . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 Using Remote Data to Discover Problem Context . . . . . . . . . . . . . . . . . . . . . . . . .33 Displaying Recent Hardware and Software Changes . . . . . . . . . . . . . . . . . . . . . . .34 Using Crash Reports to Investigate Application Problems . . . . . . . . . . . . . . . . . . .35 Comparing Overall Device Performance to Peers . . . . . . . . . . . . . . . . . . . . . . . . . .35
Chapter 6
Using Citrix EdgeSight to Resolve Network Problems

Network Problem Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Identifying Network Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 Comparing Current and Historical Network Delay For a Single Device . . . . . . . .39 Comparing the Network Delay on a Device with Other Devices . . . . . . . . . . . . . .39 Finding Machines with High Network Volume. . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Finding Network Segments with Slow Response Times. . . . . . . . . . . . . . . . . . . . .40
Chapter 7
Using Citrix EdgeSight for Planning and Implementation

Using EdgeSight for Capacity Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Capacity Planning Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Displaying the Current Resource Utilization of Machines. . . . . . . . . . . . . . . . .44 Managing Application Rollout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 Application Rollout Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 Creating a Group for Pilot Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 Displaying Current and Prior Memory Usage . . . . . . . . . . . . . . . . . . . . . . . . . .47 Displaying Prior and Current Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 Managing Multiple Application Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 Multiple Application Version Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 Displaying the Process Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Displaying Machines Running the Same Process Version . . . . . . . . . . . . . . . .49
Managing Licensing and Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 Licensing and Compliance Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 Displaying Application Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Chapter 8
Using Citrix EdgeSight Data for Analysis and Recordkeeping

Archiving Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53 Defining Archive Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 Selecting Data for Archiving. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 Determine Archiving Frequency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 Warehousing Citrix EdgeSight Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 Data Warehousing Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 Citrix EdgeSight Data Warehousing Strategy . . . . . . . . . . . . . . . . . . . . . . . . . .58 Select Data for Warehousing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Determine Warehousing Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Determine Data Storage and Disk Configuration Needs . . . . . . . . . . . . . . .60 Using Archive Reports to Warehouse Data . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
C HAPTER 1
Overview
Citrix EdgeSight is a performance and availability management solution for Presentation Server and endpoint systems. Citrix EdgeSight monitors applications, sessions, devices, and the network in real time, allowing you to quickly analyze, resolve, and proactively prevent problems. This document provides guidelines and scenarios for using EdgeSight to ensure that end users in your enterprise have the required application and network resources to work more productively. This chapter describes solutions which can be implemented using EdgeSight and lists prerequisites for effectively using this guide.
Before You Begin

You should read Citrix EdgeSight for Endpoints Introduction or Citrix EdgeSight for Presentation Server Introduction before working with the scenarios present in this document. The technical introductions to EdgeSight provide you with contextual information about EdgeSight components and how they work. The introductions also provide pointers to task-based user information that describes how to install, configure, and use EdgeSight in your enterprise. This document assumes that you are working in an environment where the EdgeSight Server is installed and has been running with alerts configured for at least one week. It is recommended that the server collect data from a minimum of 20 to 30 devices. This provides you with sufficient data to be useful in working with the scenarios.
Implementing Solutions with EdgeSight

Citrix EdgeSight collects and displays performance and availability information that allows you to isolate and resolve a wide range of application, device, and network problems. This document presents scenarios based on different types of problems and tasks. As you use these sceanarios, refer to the EdgeSight Server online help for procedures on how to use the EdgeSight Server Console and for definitions of the data displayed in reports. Before using these scenarios, review Chapter 2, Using Citrix EdgeSight Reports for basic instructions on using historical and real-time reports to display data.
Resolve System Performance Problems

EdgeSight allows you to identify, investigate, and define a resolution for performance issues affecting one or more systems from a single user interface. You can use EdgeSight to display notifications of performance anomalies, display system performance metrics over time, display hardware and software changes on systems, and display how systems are using resources such as memory, CPU, and disk. See Chapter 3, Using EdgeSight to Resolve System Performance Problems for details.
Resolve Application Problems

EdgeSight allows you to identify, investigate and define a resolution for application problems such as errors, crashes, lack of response (hangs), thrashing, and general performance issues. You can use EdgeSight to display problem notifications, display what was happening on the system at the time of the problem, list recent software and hardware changes, and compare application performance across multiple systems. See Chapter 4, Using Citrix EdgeSight to Resolve Applications Problems for details.
Resolve Network Problems

EdgeSight allows you to identify, investigate and define a resolution for network problems such as network delay, high round trip times, or Web errors. EdgeSight allows you to compare current and historical network performance for for one system or across multiple systems, to find systems with high network volume, and to identify network segments with slow response times. See Chapter 5, Using Citrix EdgeSight to Resolve Network Problems for details.
Chapter 1
Overview
Proactively Manage Hardware and Software Assets

EdgeSight does more than just help you solve problems; it can also help you in planning and implementing improvements in your enterprise. With EdgeSight, you can perform capacity planning, rollout new applications, manage multiple versions of applications, and implement licensing and compliance policies. See Chapter 6, Using Citrix EdgeSight for Planning and Implementation for applicable scenarios.
Capture and Store Data for Long Term Use

EdgeSight provides archive reports which can be transferred to long term storage for using in analysis and recordkeeping. By archiving or warehousing data, you can have continued access to long-term historical data while ensuring optimum performance from your EdgeSight Server. See Chapter 7, Using Citrix EdgeSight Data for Analysis and Recordkeeping for guidelines on archiving and warehousing EdgeSight data.
10
C HAPTER 2
This chapter describes how to access various types of Citrix EdgeSight data, both on the Citrix EdgeSight Server and Citrix EdgeSight Agent databases.
Overview
EdgeSight collects performance and availability data on each device running the EdgeSight Agent. By default, a week of historical data is retained on the agent database. Data stored in an EdgeSight Agent database on a client device is called remote data. Remote data can be accessed from the EdgeSight Server Console, as described in Accessing and Using Remote Data on page 15. Data is consolidated and uploaded to EdgeSight Server where it it used as the basis for reports, which display data using tables, charts, and graphs. EdgeSight provides a broad range of standard reports. In addition, custom reports can be created using Reporting Services. For more information on using reports, see Accessing and Using Historical Reports on page 14. Each EdgeSight Agent continuously and unobtrusively compares critical performance parameters and conditions against history. When an abnormal condition is detected, such as high memory usage, excessive network delay, or a process fault, the agent generates an alert. If the alert criteria match a configured alert rule, the agent sends a real-time alert notification to the associated server. Alerts not matching an alert rule are uploaded with the rest of the days data. For more information on displaying real-time alert information, see Accessing and Using Real Time Alerts on page 20. Process fault alert rules enable the capture and storage of crash files. For more information on using crash files, see Accessing and Using Process Fault Data on page 20.
12
Citrix EdgeSight Server Console

You interact with Citrix EdgeSight Server through the Citrix EdgeSight Server Console. The console provides you with a powerful and flexible tool for displaying availability and performance information about the end-user desktops in your enterprise. When using the console, you browse pages supplied by a Web server which display reports based on data stored in the Citrix EdgeSight database. A wide range of standard reports are available. To display the console, bring up a browser and point it to the URL for the sign-in page for your Citrix EdgeSight Server. Log in to the console using your user name (email address) and password. The following illustration shows the various components of the console. Navigation Tree Menu Bar Filter Bar
Report List Navigation TreeUse the Navigation Tree to select the specific type of operation you want to perform or the type of report you want to display. Click the plus icon or the corresponding folder name to expand that portion of the list. Once a portion of the tree is expanded, click the minus
Chapter 2
13
icon or the corresponding folder name to contract that portion of the list. Page icons indicate the type of content displayed: A report icon indicates that a report will be displayed using default parameters. These reports are often summary reports. A report list icon indicates that the console page lists reports that you can display. A remote report icon indicates that a report will be displayed based on data from a specific agent database. You must specify a device name to display these reports. A wizard icon indicates a wizard that helps you step through a procedure, such as finding reports related to specific problems. A page icon indicates that the console page is a static page rather than a report. These pages are used to specify company settings, upload reports, set user preferences, and configure EdgeSight Server. Note that the Company Settings and Server Settings menu items are only displayed if you have the required administrative privileges.
Menu BarUse the Menu Bar to perform common operations on the current page, such as adding a page to your list of favorites, refreshing a page, printing a page, or displaying help for a page. Filter BarUse the Filter Bar to refine the list of reports displayed on a page. Once you select a report, use the Filter Bar to filter report data. Depending on the report selected, filter by department, group, time period, process, device, user, site, and other data types. Filter data to isolate information based on particular classes of processes, devices, or users and to quickly identify problems or trends. You can also filter data on nonreport pages such as the Current Alert List or the administrative and configuration pages. Click Go to apply filter parameters. Report ListUse the Report List to select a report for display. You can filter the list using the Filter Bar, or sort the list as required. Once a report has been generated, it is displayed in this area.
14
Accessing and Using Historical Reports

EdgeSight provides a set of historical reports that display availability and performance data. Reports are organized by the subject of the data in the report: users, devices, processes, or sites and transactions. Under these subject containers, reports are grouped by the type of information displayed about the subject: performance (resource usage and login times), stability (errors and system events), and network (delay, round trip time, volume, and ICA-related data). These groupings help you locate the reports you need. For example, if you wanted to display the server-side session startup times for a specific user, you would navigate to Users > Performance > Sessions and select the Server Startup Time for a User by Day. Or, if you wanted to display which processes were recently experiencing the most errors, you would navigate to Processes > Stability > Errors and select the Most Process Errors for a Group by Process. As you work with EdgeSight, you may find that you use some reports frequently. You may want to add these reports to your My Reports page for easy access. See the My Reports List online help topic for more information on using the My Reports page.
Finding Reports Using the Support Wizard

If you are unsure which report to use, you can use the Support Wizard page to help you select the correct report based on the problem you are investigating. Select Support Wizard from the navigation pane to invoke the wizard. The wizard guides you to the applicable report for your problem. See the Support Wizard online help topic for more information on using the wizard.
Finding Related Reports

When investigating a problem, you may want to display related types of data to help put information in context. For example, when investigating a problem with network response time for a specific site, you first display network delay data using the Network Delay for a Site by Day report. By clicking on the Related Reports link, you can quickly navigate to reports which display network volume or round trip time for the same site. See the Working with Reports online help topic for more information.
Chapter 2
15
Accessing and Using Remote Data

Remote device access enables you to drill-down to each EdgeSight agent database to execute real-time queries against the agent. (See Using Real-Time Reports on page 15 for information on displaying data from an agent database.) Since remote access to EdgeSight agents enables you to remotely affect the machine behind the firewall, remote access has some requirements that must be met: ActiveX Control must be downloadedRemote Access is accomplished through OLE-DB and an EdgeSight OLE-DB Provider. We group this DLL in a cabinet file with a charting control to enable remote access to your devices. Remote NT administrative privilegesUnless your EdgeSight Server administrator has changed the default agent settings, administrative privileges are required on the device you are accessing.
Workers are units of execution in each EdgeSight Agent, typically scheduled to run at specific times of the day and when the machine or user is idle. You can remotely execute a worker when required. You can execute the following workers remotely: Data UploadThe Data Upload worker uploads all of the information from the EdgeSight Agent to the EdgeSight Server. This worker typically executes on a regular schedule to upload performance, usage and other asset information to the server. The Data Upload worker, depending on the activity of the computer, can consume noticeable resources so it should be used with care. Configuration CheckThe Configuration Check worker instructs the EdgeSight agent to check the EdgeSight Server for changes in its configuration. For example, new alert notifications or a change in the worker schedules.
Using Real-Time Reports

This section provides information on using real-time reports (Real Time > Remote) for end-user devices or Presentation Server systems. These reports display information from the selected Citrix EdgeSight Agent database using Microsoft Excel spreadsheets. These reports are interactive, customizable, and extensible.
16
Real-time reports provide detailed information about the performance of specific devices. While historical reports help you assess trends across groups of systems, real-time reports help you resolve performance problems on specific systems. Real-time reports provide data that is both granular and recent, allowing you to investigate problems thoroughly and in a timely fashion. By connecting directly to a Citrix EdgeSight Agent database, the data available is of a finer granularity than that stored in the server database. By displaying the remote data in an Excel spreadsheet, you can customize and build your own views and graphics into the enormous amount of data that is captured by Citrix EdgeSight agents. Real-time reports display data in both five minute slices and 5 second slices depending on how large a time period of data is selected in the query. In addition, data is available as it is collected, with no need to wait for data to be uploaded to the server. EdgeSight provides the following types of real-time information: Summary Various summary graphs for a quick overview of what has been happening on the machine. AlertsDetailed alert information for the device over specified time period, including system performance and context at the time that the alert condition occurred. SystemMemory, processor, network, and I/O statistics and the default perfmon performance counters. System Compare and Presentation Server SummaryDisplays performance counters from multiple devices for use in comparing system performance. The data is presented by device and also by counter, allowing you to view overall performance for each system or to directly compare counter values across systems. NetworkDetailed network performance information (volume, round trip time, and delay) by host, application, protocol, or user over the specified time period. Presentation Server User SummarySystem, session, and application performance counters for a specified user and Citrix Presentation Server system.
In addition to these reports, you can also perform a trace route, display a process list for a device, or find the EdgeSight Server associated with a managed device. The following scenario describes how you might use real-time reports to resolve a performance problem:
Chapter 2
17
There are indications that a device is at risk for experiencing performance problems. These indications could include the device appearing as a leader in a memory usage report, or a sharp increase in the number of memory-related alerts or a user calling you and complaining of a system problem. A first step might be to invoke the Summary report to inspect the overall state of the system. You can adjust the timeframe of the report to show more data as required. To adjust the timeframe, navigate to the Start sheet, change the start and end times and click Update. (By default, the start time is set for 7:00 AM of the current day, and the end date is set to the current date and time.) Spikes in resource usage may indicate a specific area and timeframe for further investigation. Next, you can display the System report and look at memory-related performance counters. Double-clicking on a data point in the chart displays process performance for the related time period which may expose high memory usage by a particular process. After drilling down to display process performance data, you can select another counter to display using the Counter drop-down menu or change the number of processes display by changing the value in the Top field. This enables you to broaden your investigation to look at different aspects of performance and a larger set of applications. You can also approach the problem from the point of view of looking at specific alert conditions. Display the Alerts report and double click on a memory-related alert to display performance counters and device context before and after the alert was generated. Three graphs are displayed showing CPU and memory, I/O, and network statistics. The red line on the graphs indicates the time that the alert condition occurred. A table of applications and tasks indicates what applications the user was using prior to and slightly after the alert occurred. In some cases, you may want to compare the device performance with another device to determine whether the problem is specific to the device in question. Use the System Compare report to display data for multiple endpoint devices, or the Presentation Server Summary report to display data for multiple Presentation Servers. You can first compare the overall performance for each device and then directly compare specific counters on both devices. You can specify a list of devices in which you are often interested and set the start and end date and time to capture the last fifteen minutes of data. The resulting report serves as a very powerful real-time dashboard. Once the spreadsheet is configured the way you want it, you can save it for reuse at a later date. As you can see, real-time reports provide quick access to detailed data and give you a means to investigate a problem from multiple perspectives.
Real-Time Report Components

Each real-time report is made up of multiple Excel sheets of the following types: StartDisplays the Device Selection dialog, which is preloaded with the name of the selected device and start and end dates and times. Use the Start
18
Date and End Date fields to adjust the time frame for the report. Click Update to redisplay the chart after entering the new dates or changing the device name (directly from the spreadsheet). By default the spreadsheet sets the start date to 7:00 am of the current day and the end-date to the current time. ChartDisplays charts showing performance counter data. Click on data points in charts to drill down to related or more detailed data. Depending on the report, there may be multiple chart pages. DataDisplays the five-second or five-minute data underlying the charts. For many of the charts different granularities of data are displayed depending on how large a time period is queried from the remote device. If you select a large period time and the Citrix EdgeSight agent were to try and return a large dataset then it would take too much memory, time, network bandwidth and, most importantly, would overburden the remote device. Note that in some spreadsheets the data is captured and populates the same sheet as the graph, while other spreadsheets record the entire recordset as a separate underlying sheet. It depends on how the data is organized on the remote database and how it is retrieved.
Displaying Real-Time Reports

Real-time reports are available under the Remote folders in the Citrix EdgeSight Server Console. When you first invoke a remote report after logging in to the console, you must select a device. After the first real-time report is generated, subsequent reports use the selected device as a default until you select another device. Once a device is selected, the report is generated using a default time frame of the current day, starting at 7:00 AM and ending with the current time. You can edit the start and end dates and times to display more or less data. Select the Start tab, edit the Start Date and End Date values, and click Update to regenerate the report. The amount of data available for display depends on the agent configuration. The default is to retain eight (8) days of data. Different granularities of data are displayed depending on how large a time period is queried from the remote device. Many of the charts in the real-time reports are interactive. Double-click on a data point to drill down to more detailed information. The following table describes what details are available for display.
Report Alerts System Click on A specific alert A data point in any chart To display details about CPU, memory, I/O, and network statistics at the time of the event, plus end-user application context Process performance on the selected device
Chapter 2 System Compare (endpoint devices) or Presentation Server Summary Network Performance A data point in the endpoint performance chart for a device A data point in a volume chart A data point in a delay/ RTT (round trip time) chart A data point in any chart
19
Process performance on the selected device
Presentation Server User Summary
Connection and transaction volume by host, application, protocol, or user Connection and transaction delay by host, application, protocol, or user Process/session performance
Customizing Reports
When using the System Performance or System Compare reports, you can change which counters are shown in a chart and, in some cases, add counters to a chart. This capability is most useful when using real-time reports to actively investigate a problem. You can also customize a report using the embedded Visual Basic for Applications (VBA) source code. Adding a counter is the easiest way to display more data in a chart. For example, open the System Performance report for a device. Note that the performance counters are listed in the table to the right of the chart. If the table is full, you must replace one of the existing counters to display a new counter. Navigate to the SysPerfCompute sheet and select the name of the counter you want to add to a chart. (It is best to use the computed data rather than the raw data found in the SysPerfData sheet.) Copy the counter name, return to the SysPerfChart sheet and paste the counter name into the table. Set the scale value as required. In most cases, the relationship between performance counters is more important than the absolute values. Decreasing the scale values for those counters with high absolute values provides a more easily readable chart. Return to the Start sheet and click Update to refresh the report and display the new counter on the chart. The Visual Basic for Applications (VBA) code is embedded in each report, allowing you to use the Visual Basic Editor to edit the code that retrieves the data from the remote device and generates the charts. Open the report you want to modify and select FileSave As from the browser menu to save a copy of the report. For information on Excel, see Office Developer Center: Excel at http:// msdn.microsoft.com/office/understanding/excel/. For information on VBA, see ISV Community Center: Visual Basic for Applications at http://msdn.microsoft.com/isv/technology/vba/default.aspx.
20
Accessing and Using Real Time Alerts

If a Citrix EdgeSight Administrator has configured alert rules, real-time alert notifications are delivered to the server and displayed on the Current Alert List (Real Time > Alerts > Current Alerts). Consider the following when using the Current Alerts List: Real-time alert data is available on the console for three days if the default database grooming configuration is used. Real-time alerts are designed to notify you of critical events which require action. In most cases, underlying problems have been addressed or escalated before alerts are removed from the database. Some alerts require extensive data collection, such as process faults or snapshots. Although the alert may be displayed on the console, the associated crash files are only available on the console after data collection is complete and the files hasve been uploaded to the server. In some cases, depending on the event, the state of the machine running the agent may not allow for data collection. In these cases, the alert will appear on the console, but crash files are not available.
Accessing and Using Process Fault Data

When a process fault occurs on a device, the EdgeSight Agent captures contextual information for the machine and the application, if available. In addition, the agent captures a memory dump, stack traces, and a detailed module list for the failing application. Information on process faults is collected primarily when the fault occurs. Additional information, such as resource usage data, is collected later. The agent checks the configuration requirements previously downloaded from EdgeSight Server. If a process fault alert has been configured for the failing process, the files are compressed into special payloads and uploaded to the server whenever network bandwidth is available and system resources are free. The crash report is available in the following formats: Crash details (ASP page) XML report (XML file) Mini dump (DMP file) Crash CAB (contains the XML and DMP files)
Chapter 2
21
Capturing Context at the Onset of a Performance Problem

One of the biggest challenges in troubleshooting performance problems as reported by end-users is in understanding the underlying context in which the problems are occurring, specifically what applications and processes are running and how those processes are impacting overall performance. Historically, EdgeSight captured data automatically when an application crashed. But in many cases users report problems when processes run-away and the application or system goes into a hung state. EdgeSight for Endpoints provides the ability to take a remote snapshot at the onset of a performance problem. This feature allows you to remotely analyze the current state of the end-users system, identify a potential problem and capture a full set of diagnostic data that can be shared internally with the application owner or externally with a third-party vendor to troubleshoot any potential problems within the application. To perform a remote snapshot: 1. Navigate to Real Time > Remote > Processes. Click the Device icon to bring up the Device Picker. Select the device on which the problem is occurring and click OK. This displays a list of all processes currently running on the device. Locate the process for which the snapshot is required. Click the menu button and select Generate Snapshot from the pop-up menu. Choose Normal or Full from the submenu to generate a diagnostic snapshot (dump file) for a process. The snapshot is generated on the selected device and then uploaded to the server as an alert. You can display the resulting dump file from the Alert Console. Dump file delivery times depend on the process selected, and on system and network performance. Alerts may appear on the console before the dump files are delivered. Note: In most cases, you will select Normal. Keep in mind that selecting Full generates a full process dump, which is as large as the selected process. Full snapshots consume end-user system resources and may result in a discernable impact on system performance. 4. Navigate to Real Time > Alerts > Current Alerts. Locate the Snapshot alert associated with the process. Click the menu button and select the type of data you want to view (Crash Details, XML Report, Mini Dump, or Crash CAB). You can also select Remote to display alert data directly from the agent database.
2. 3.
22
C HAPTER 3
This chapter provides a general procedure for identifying, investigating, and resolving system performance issues identified by Citrix EdgeSight. Performance issues can be difficult to evaluate. Given a users complaint, a support person would have to login to the users machine remotely or locally and run certain tools to track down pertinent information. Task Manager can show current processes and their resource and network usage. System Monitor can be used to evaluate multiple potential performance bottlenecks. Event Viewer can be used to find certain errors. These are useful tools, but they require the support person to login or connect to the system to evaluate the situation, and most only do realtime reporting with no ability to compare to historical data. EdgeSight provides a centralized console for use in investigating performance problems and offers a wide range of both real time and historical reports. This chapter covers the following topics: System Performance Scenario Displaying Recent Alerts Displaying the Historical Performance for a Device Display Asset Changes Display Resource Utilization Information
System Performance Scenario

Your Level Two support person receives a ticket regarding a users machine that seems to be running slowly. To track down the source of the problem, he needs the answers to the following questions: Have there been any errors or not-responding messages on the machine? If so, which application is encountering problems? To which servers was the application connected at the time?
24
What other processes were running at the same time and were they tying up resources?
What is the general system information for the machine (such as CPU, total memory, operating system version, and make and model)? Were there any changes on the system (software or hardware) before the user started experiencing performance degradation? How much hard drive space is available? Generally, how much memory and CPU has the system been using during the course of a work day? How does this compare to last month when the system was running well?
EdgeSight makes gathering all of this information possible from a single console without requiring the support person to login to the users machine. It also provides historical data so that the support person can detect trends in performance data and evaluate where and when things might have changed. The support person should start by checking the Current Alert List to see if there are any errors, faults or not-responding alerts. They can then drill into the details of the alerts and connect remotely to the machine to display data from the EdgeSight Agent database. From here they can see process information and network connections as they looked at the time of the error.
Use the Performance Summary for a Device report to display
charts on CPU, memory, page fault, and disk space.

Use the Assets for a Device report to gather information about the users system, such as the operating system version, CPU speed, available memory, and hardware make and model. Use the Asset Changes for a Device report to display any changes that have occurred on the system, such as hardware changes or newly installed
Chapter 3
25
applications. These changes could give clues as to the source of the performance degradation. The following reports should also be generated in order to check possible performance bottlenecks. These can be compared to the historical data retrieved over the last month. Disk Usage for a Device by Day Memory Usage for a Device by Day System CPU for a Device by Day
You may also want to check the following reports: New Processes for a Device Process Errors (or Process Faults) for a Device by Day Compare the errors or faults to those displayed in the real time data.
Displaying Recent Alerts

Alerts are notifications of events or adverse performances trends occurring on managed devices. Check the Current Alert List for errors, process faults, or not responding messages. 1. 2. 3. Navigate to Real Tme > Alerts > Current Alert List. Use the filter to narrow the results to the users device by typing the device name in the Filter field and selecting the By Device radio button. Read through the various alerts for the device and try to determine if any of these might be the cause of performance degradation. Alerts of interest can include process alerts, such as a Thrashing process alert or a Process hung alert, or system alerts, such as a System low resources alert. Expand alerts for more detail. Click the menu icon and choose Remote to connect remotely to the device and display process, performance, network, and memory data as it looked at the time of the error.
4.
Displaying the Historical Performance for a Device

Use the Performance Summary for a Device report to display historical performance for the device, including CPU, memory, page fault, and disk space. By default, this report provides performance data for the last week.
26
1. 2. 3.
Navigate to Devices > Performance > Performance Summary for a Device. Type or browse for the name of the system in the Device field and click Go. Click on a data point in any chart to display detailed data for the associated performance metric.
Display Asset Changes

Gather general information about the system and then find out about recent software and hardware changes: 1. 2. Navigate to Devices > Configuration > Assets for a Device. Type or browse for the name of the system in the Device field and click Go. This will give you general information about the system, such as the operating system version, CPU speed, available memory, and hardware make and model. This information is derived from WMI. Expand any asset categories displayed to see additional details. To find out what has changed on a system, both hardware and software, navigate to Devices > Configuration > Asset Changes for a Device. Expand any asset categories displayed to see additional details.
3. 4.
Display Resource Utilization Information

Check memory, CPU and disk performance for potential bottlenecks. In any of these reports, you can change the date range in the filter to compare recent performance to historical performance. 1. 2. 3. Navigate to Devices > Performance. Open the Disk report list and run the Disk Usage for a Device by Day report to find out if the hard disk is almost full: Open the Memory report list and run the Memory Usage for a Device by Day report to see what percentage of the total system memory is being utilized on average. You can also see here how many processes have been running. Open the Disk report list and run the System CPU for a Device by Day report to see the percentage of CPU usage on average.
4.
C HAPTER 3
This chapter provides a general procedure for identifying, investigating, and resolving Presentation Server session performance issues identified by Citrix EdgeSight. This chapter covers the following topics: Session Performance Scenario Displaying Session Latency Data Displaying Round Trip Time Data Displaying Client and Server Session Startup Time Data Displaying Real Time Session Performance Data
Session Performance Scenario

A user reports problems with the availability and response time of applications provided by a Presentation Server. You have looked at the system performance metrics for the specific server, but have not discovered likely causes for the problems. (See Chapter 3, Using EdgeSight to Resolve System Performance Problems for information on using EdgeSight to evaluate system performance.) The nexp step is to investigate how the users sessions are performing: What level of session latency is the user experiencing and how has it changed over time? How does the level of session latency compare to other users?
What is the ICA session round trip time and how has it changed? What are the session startup times from both the client and server perspective?
EdgeSight provides session performance data in historical reports, including
28
session startup time for both server and client. Performance data is also available from a network perspective, such as latency, ICA round trip time, and ICA traffic. EdgeSight also provides session experience monitoring (SEMS) metrics which show the health of a system from the point of view of an end user. For example, a Presentation Server metric may report that the server has reached a high percentage of CPU utilization. From the users point of view, if their applications remain responsive and their overall experience of using the system is acceptable, then CPU utilization may not actually be a problem. In another instance, the Presentation Server metrics may not indicate a problem, but a fault between the Presentation Server and the end user may be causing severe usability issues. The collection of SEMS data is dependent on the following set of software components: EdgeSight 4.5 Agent running on the Presentation Server Presentation Server 4.5 Enterprise or Platinum Edition ICA client version 10 or greater
Displaying Session Latency Data

ICA session latency is based on the last recorded latency measured for the session (Latency - Last Recorded). The samples recorded by the agent are consolidated to one hour intervals in the data uploaded to the server. To display session latency data:
1. 2. 3. Navigate to User > Network > ICA > ICA Session Latency for a User by Day. Type or browse for the name of the user in the User field and click Go. The report is displayed, showing both average and peak session latency by day. Expand any row of the report to break down latency by session.
You may also want to compare the latency for this user against the latency for other users. Return to the list of ICA reports and select Highest ICA Session Latency for a User Group by User. Expand any row of the report to display session details and latency.
Displaying Round Trip Time Data

When using round trip time (RTT) metrics to diagnose session problems, it is important to recognize the two types of round trip time: network RTT and ICA RTT.
Chapter 3
29
Network round trip time (RTT) is based on network latency. Network latency is the detected network latency between the ICA client device and the Citrix Presentation Server. Unlike the ICA round trip metric, the network round trip is largely independent of processing time on the client or server. The ICA round trip time is the time interval measured at the client between the first step (user action) and the last step (graphical response is displayed ), as calculated by the session experience monitoring service. The ICA round trip metric can be best thought of as a measurement of the screen lag that a user experiences while interacting with an application hosted in a session on a Presentation Server. To display round trip time data: 1. 2. Navigate to User > Network > ICA > ICA Round Trip Time for a User by Day. Type or browse for the name of the user in the User field and click Go. The report is displayed, showing both average and maximum network and ICA RTT by day. Expand any row of the report to break down RTT by session.
3.
Displaying Client and Server Session Startup Time Data

Client startup time is the time elapsed from the time of the request (mouse click) to the time when the ICA connection between the client device and Presentation Server has been established. In the case of a shared session, this duration will normally be much smaller, as many of the setup costs associated with the creation of a new connection to the server are not incurred. Server startup time is the time spent on the Presentation Server performing the entire start-up operation. In the event of an application starting in a shared session, this metric is expected to be much smaller, as starting a completely new session involves potentially high cost tasks such as profile loading and login script execution. To display session startup time data: 1. Navigate to Users > Performance > Sessions. Depending on which type of statup time you want to display, select either the Client Startup Time for a User by Day or Server Startup Time for a User by Day report. In either case, type or browse for the name of the user in the User field and click Go. Expand any row of the report to break down startup time by session. Client and server startup times are high -level metrics and include a number of specific steps in the startup process. To display the component metrics
2. 3. 4.
30
for startup times, return to the Sessions report list and select Startup
Time Detail for a User by Session.

5. Expand any row to display startup details. Because of space constraints, abbreviations are used for session experience monitoring metrics. Move you mouse over each heading to display the full name of the metric. For descriptions of each metric, see the Report counters Glossary topic in the EdgeSight Server online help.
Displaying Real Time Session Performance Data

The historical reports help you monitor performance trends and compare performance across groups of systems. EdgeSight for Presentation Server also provides highly granular, real time session experience monitoring data that enables you to display information about an active session. To display real time session performance data: 1. 2. 3. Navigate to Real Time > Remote > Presentation Server User Summary. Click the user icon to display the Presentation Server Session Wizard. Select the Query one or more farms directly radio button. This is
the recommended method for locating an active session for a specific user. This method requires existing credentials for logging in to the selected farms.
4. Select the checkbox next to the farm name to select a farm to be queried. If necessary, filter the list of farms by department or group, or farm name. Note that you can only select farms for which default credentials have been defined, as shown in the Credentials column. Click Next. Select a user session from the list and click Next. Click the checkbox next to the devices to be included in the report. Click Finish to display the report. Note that by default, the report only displays the last 15 minutes of data. You can change this time period as required. Click on a data point in the Session Performance chart to display additional details, including client and server startup times.
5. 6.
7.
C HAPTER 4
This chapter provides a general procedure for identifying, investigating, and resolving application issues identified by Citrix EdgeSight, in this case, a process fault. Although the scenario is based on a specific problem, the basic steps of the procedure can be applied to a range of application issues. This chapter covers the following topics: Application Problem Scenario Problem Notification and Initial Investigation Using Remote Data to Discover Problem Context Displaying Recent Hardware and Software Changes Using Crash Reports to Investigate Application Problems Comparing Overall Device Performance to Peers
Application Problem Scenario

This scenario involves several levels of IT department personnel. The specific titles, responsibilities, and escalation procedures may be different for your business. Help deskResponds to user requests for assistance, gathers problem context, and escalates problems as required. Application supportInvestigates application problem using devicespecific data and configuration information. Escalates problems as required. Application developerInvestigates application problem using detailed application-specific data such as crash reports.
32
This scenario assumes the following: An alert rule has been created for Process Fault conditions. The alert rule has an associated alert action that results in a notification email being sent to the help desk. Refer to the Alert Rules Setup topic in EdgeSight Server Online Help for information on creating alert rules and specifying alert actions. Help desk and/or application support personnel have been granted administrative privileges on the remote device. Receive NotificationA help desk support person receives email notification of a crash of a critical application in their business unit. The help desk support person navigates to Real Time > Alerts > Current Alerts and selects the real-time alert corresponding to the end users problem. This step provides a starting point for the problem analysis. If the problem resolution is not readily apparent, the issue is forwarded to application support. Collect Historical ContextThe application support person navigates to Real Time > Remote > Alerts for the device and looks at the context of the alert. Identify Recent ChangesThe tech will also go to Devices > Configuration > Software Asset Changes for Device (and also the corresponding report for hardware) to see what recent changes have been made to the device. An additional view of what may have changed on a group level is provided by Processes > License & Utilization > New Processes for a Group. Collect and Forward Data to Application DeveloperThe issue can be forwarded to an application support specialist if required. The crash report provides detailed contextual information about the state of the device before and at the time of the crash plus a crash file. Compare Device Performance to PeersSupport personnel use Devices > Performance > Performance Summary for a Device to provide an overall view of the device. The Performance Summary by Device report can be used to compare the devices performance to that of its peers.
The steps in the scenario are as follows: 1.
2.
3.
4.
The following step can be performed if necessary: 1.
Chapter 4
33
Problem Notification and Initial Investigation

A help desk support person receives email notification of a crash of a critical application in their business unit. The help desk collects basic information as specified in the companys problem report procedures to help identify the specific issue. Then, the technician uses the Citrix EdgeSight Server Console to display more information about the problem. The Current Alert List displays information about incoming real-time alerts from end-user devices. When an alert condition is detected, the Citrix EdgeSight Agent generates an alert and, if a matching alert rule is configured, sends a notification to the server. 1. From the EdgeSight Console and navigate to Real Time > Alerts > Current Alerts. Real-time alerts are displayed, beginning with the most recent. By default, real-time alert notification are retained for three days, after which they are groomed from the database. Filter the alerts by user or device to narrow the number of alerts displayed. You can also filter by alert type or alert name. Locate the alert corresponding to the reported problem. Click the expand icon to expand the alert and display a description of the problem. The Device Time field can help you pinpoint the time of the fault in relation to other events taking place on the device. If access to the agent database is allowed, click the menu icon and select Remote from the pop-up menu. For more information on using remote data, see Using Remote Data to Discover Problem Context on page 33. Forward the issue to application support for more in-depth analysis, if required. To route the alert, click the checkbox in the first column of the alert table and then click Route. The Route Alerts wizard is displayed. Note that the selected alerts are listed at the bottom of the page. Complete the wizard and click OK to route the alert.
2. 3. 4.
5.
6.
You can also use the categorized alert reports (Real Time > Alerts > Alert Reports) to display filtered alert information. In this scenario, the Alerts for a Group By Process or By Device reports are applicable.
Using Remote Data to Discover Problem Context

Remote data is stored in the EdgeSight Agent database. Remote device access enables a technician to drill down to an EdgeSight agent database and execute real-time queries to display the application and device context at the time the problem occurred.
34
Note Unless your EdgeSight Server administrator has changed the default agent settings, administrative privileges are required on the remote device to be able to display a remote report.
1. 2. An alert is routed from the help desk to application support for further investigation. From the EdgeSight Console, navigate to Remote > Alerts, and filter on the device. The Remote Alerts report shows the alert information stored in the EdgeSight Agent database for the device. The default time period is the current day, starting at 7:00 AM. Depending on when the problem occurred, you may need to select a longer time period to display the specific alert. Click on an alert to display contextual information, including CPU and memory usage, I/O statistics, network usage, and task history. Click on a data point in the CPU and memory, I/O, or network charts to display additional detail. Each type of contextual information supplies a different view of the system environment leading up to the alert condition. For example, task history can detail user-initiated tasks which may have contributed to the problem, while system performance metrics can expose CPU or memory usage levels which may indicate a poorly performing system. In addition to the contextual information, examine related previous alerts. In some cases, an alert can be preceded by related alerts indicating a problem with an application. For example, application fault alerts are sometimes preceded by application not responding errors.
3.
4.
You can also investigate system changes (both hardware and software), as described in the next section.
Displaying Recent Hardware and Software Changes

Another area for investigation is changes in the system configuration, both hardware and software. In some alert configurations, events such as hardware changes and the running of new applications generate alerts. If this is the case in your environment, navigate to Real Time > Alerts > Current Alerts and look for Plug and Play Hardware Change and New Process alerts associated with the device. You can also use the asset change reports to display a history of recent system changes. In the case of an application fault, look for the following types of changes: A new version of a module used by the faulting application A change to a system or registry setting which may affect the application
Chapter 4
35
1. 2.
Navigate to Devices > Configuration > Software Asset Changes for Device and filter on device. The software assets for the device are listed. Click All Changes in the Asset Summary table to display recent software changes on the device. Note that the class listed is a link to the applicable application class documentation. Navigate to Devices > Configuration > Hardware Asset Changes for Device and filter on device. The hardware assets for the device are listed. Click All Changes in the Asset Summary table to display recent hardware changes on the device. An alternate view of what has changed in the environment at the group level is provided by the new processes report. Navigate to Processes > License & Utilization > New Processes for a Group to display the newest applications.
3. 4. 5.
Using Crash Reports to Investigate Application Problems

When a process fault occurs on a device, the EdgeSight Agent captures contextual information for the machine and the application, if available. To access the crash files, navigate to Real Time > Alerts > Current Alerts and locate the real-time alert corresponding to the end users problem. Click the menu icon and select the crash report menu item in the desired format. Note that this information is not avalable in all cases, depending on the nature of the system crash. Also, the alert may appear in the Current Alert List before data collection has been completed.
Comparing Overall Device Performance to Peers

In some cases, it can be helpful to look at the overall health of the device where the problem occurred. Comparing a devices performance to that of its peers can help determine whether the problem was isolated to a single device or is related to factors affecting similar devices. If you use custom groups for comparison purposes, you can use an existing custom group or, if you have administrative privileges (particularly the Edit Public Groups permission) on the EdgeSight Server, you can create a new custom group. 1. 2. Navigate to Devices > Performance > Performance Summary for a Device to provide an overall view of recent device performance. Custom groups are useful in performing comparisons between a single device and some set of related or similar devices. Navigate to Company
36
Settings > Server > Device Management > Groups and create a group for comparison, such as a group of machines with the same operating system, or machines performing similar tasks. 3. Navigate to Devices > Performance > Performance Summary by Device and filter on the group containing the device on which the problem occurred to see how the device compares to other devices in the group. If further investigation is required, application support can route the alert to an application developer with a request to examine crash reports.
C HAPTER 5
This chapter provides a scenario for using Citrix EdgeSight data to identify, investigate, and resolve network problems. Supporting the network can be difficult when all too frequently we are left with little or no information about the performance of the network, such as metrics on where the most traffic is being generated from, what the average delay is from a branch office to a server at headquarters, or which applications are most responsible for network volume. In addition, this information is rarely in a central location. With EdgeSight, network performance metrics are continually being measured. This makes it easy to retrieve historical network activity and compare that to recent data to help determine the source of network latency or other issues. Additionally, tools such as TraceRoute can be initiated on any device from the EdgeSight Server Console without visiting the machine. This chapter covers the following topics: Network Problem Scenario Identifying Network Problems Comparing Current and Historical Network Delay For a Single Device Comparing the Network Delay on a Device with Other Devices Finding Machines with High Network Volume Finding Network Segments with Slow Response Times
Network Problem Scenario

The network administrators team at a large company just received a call from one of the users in a branch office. They are complaining that the response time when trying to connect to a server at the home office is unusually slow. The network administrators know that there are some bandwidth limitations on that connection, but that network performance should not be as bad as the user describes.
38
The network administrators want to answer the following questions in order to help isolate the problem: Does the network delay (latency) on the users machine indeed differ today compared to a week ago? Are other users in the branch office experiencing delay to that same server? Are other users in other offices experiencing delays to that server? Are any machines at the branch office generating an unusual amount of network volume that could be restricting bandwidth? If so, which application is responsible for the volume? Of all of the segments between client and server, which seems to be especially slow?
Identifying Network Problems

EdgeSight can provide network performance information from the server console without having to visit the various machines in question. For example: To determine whether the users machine is indeed experiencing more delay today than during any previous time, display the Network Delay for a Device by Day report. Expand from this report to see which servers the user was connecting to that was experiencing the greatest delay. To determine if other users from the branch office are experiencing delay to the same server, display the Network Delay for a Group by Day or the Network Delay for a Site by Day reports. The group that is used to filter these reports should be the group that represents the branch office. Run the same reports for other branches to determine if the delay is isolated to a single branch. To determine if any machines in the branch office are generating an unusual amount of network volume, display the Highest Network Volume for a Group by Device report. To determine which application is responsible for the network volume, run the Highest Network Volume for a Group by Process report. To determine which segments between client and server are responding slowly, run the TraceRoute utility from the EdgeSight console.
Chapter 5
39
Comparing Current and Historical Network Delay For a Single Device

One of the first tasks is to place the current performance of a device in context. Finding out when the poor network performance started to occur, or finding a pattern of poor network performance over time, can help isolate likely causes.To determine if the device is experiencing an unusual amount of delay, perform the following steps: 1. 2. 3. 4. 5. Navigate to Devices > Network > Delay and select the Network Delay for a Device by Day report. Enter the target device name in the Device field, or click the device icon and select the device name from the list. Specify a time rage using the Start and End fields. Click Go to generate the report. The resulting report shows average network delay for each day in the specified time range. Compare the average delays to the most recent day to determine if the users complaint seems legitimate. Expand any date to display detailed network delay metrics. This allows you to determine what sites are associated with the longest network delays.
6.
Comparing the Network Delay on a Device with Other Devices

Once you have determined that the device is running into excessive network delays, it is useful to determine if the problem is shared by others at the same branch office. 1. 2. 3. Click Delay in the navigation tree to return to the list of Delay reports. Select the Network Delay for a Group by Day report. Locate the target group of devices. Depending on your sepcific deployment, this can be a department or a custom group of devices. (If no department or custom group maps to the devices in the branch office, you may need to create a custom group as described in the Citrix EdgeSight Administrators Guide.) Specify a time rage using the Start and End fields. For ease of comparison, you may want to use the same time period as when displaying the report for the single device. Click Go to generate the report.
4.
5.
40
6. 7.
Expand any date to display detailed network delay metrics. This allows you to determine which devices were experiencing significant delay. You may also want to display this report against other groups of machines to determine if the problem is isolated at the branch office, or is occurring in other offices as well.
Finding Machines with High Network Volume

It can be useful to identify machines with a high network volume that may be contributing to network delay. 1. 2. 3. Click Volume in the navigation tree to display the list of network volume reports. Select the Network Volume for a Group by Day report. The same department/group and time period parameters are used as in the last report. The report indicates which machines are generating the most volume. This can help determine if any machines are directly responsible for any delay on the WAN connection. If you wish to determine which applications are generating the volume, navigate to Processes > Network > Volume and display the Highest Network Volume for a Group by Process report.
4.
Finding Network Segments with Slow Response Times

Once you have identified devices of interest, you can run the Trace Route utility against devices to which segments between client and server are responding slowly. This utility allows you to initiate a Trace Route from any device monitored by EdgeSight to any destination host without having to visit the command line of the device. Trace Route provides the return times on each segment along the way to the destination. 1. 2. Navigate to Real Time > Remote > Trace Route. Enter the target device name in the Device field, or click the device icon and select the device name from the list. This is the device from which the Trace Route will originate. In the Host field, enter the name or IP Address of the server that will be the target for the Trace Route. Place a check in the box next to Lookup Names if you wish to resolve the names of each of the routers/servers along the trace route. Leaving this unchecked will perform the trace more quickly. Click Start Trace.
3. 4.
5.
Chapter 5
41
6.
The results give you the average return time of each segment. This information can be used to help determine if there is a particular segment along the path between the users machine and the server that may be causing the latency.
42
C HAPTER 6
This chapter provides scenarios for using Citrix EdgeSight data to manage software and hardware changes in your environment. This chapter covers the following topics: Using EdgeSight for Capacity Planning Managing Application Rollout Managing Multiple Application Versions Managing Licensing and Compliance
Using EdgeSight for Capacity Planning

Proper capacity planning ensures a healthy computer network that can grow to meet future needs. Each team or business unit in an organization will have different needs, both current and future. They should have the tools available to evaluate existing performance and utilization and be able to determine if certain machines need to be upgraded or if the entire hardware base can handle the deployment of a new application. Capacity planning can be difficult to gauge accurately, but with EdgeSight performance and availability monitoring, this process is greatly simplified.
Capacity Planning Scenario

The Sales division of a bank wants to evaluate the current capacity of their Windows desktops for two purposes: 1. In the short term, to be proactive in supporting the user base. A. 2. If any systems show near maximum resource usage of memory, CPU, or disk, then they can proactively upgrade those systems.
Longer term, they want to evaluate the ability to handle the deployment and usage of a new CPU and memory-intensive application.
44
Having already evaluated the new application and determined the CPU and memory requirements, the IT support team for the Sales division needs to determine which users, if any, will need more memory or faster CPUs in order to comfortably use the new application. They can do this by adding the resource requirements of the new application to the current average resource usage on each machine. Compare that to the determined minimum baseline and you can easily extrapolate which machines do not have the required capacity. EdgeSight can give the IT support team the current average resource utilization for each machine in the Sales division. This is most often the key missing piece of information. The IT team may have the requirements of the new application and know what the minimum baseline resource usage is, but do not always have the real usage data from desktops. To display the required information on actual resource usage, navigate to Device > Performance and go to the specific report list for the resource (CPU, Memory, or Disk).The summary reports (CPU Summary, Memory Summary, and Disk Usage Summary) are particularly useful in displaying an overall view of resource usage. Filter the results of these reports by choosing the Sales department from the filter drop-down list.
Displaying the Current Resource Utilization of Machines

To see how a group of machines are currently utilizing resources, perform the following steps: 1. 2. Navigate to Device > Performance and go to the specific report list for the resource (CPU, Memory, or Disk). After clicking on the CPU Summary report, go to the filter and choose the appropriate department from the filter drop-down box in order to only view machines from the relevant group. The CPU Summary report categorizes the devices by CPU speed. Notice that the machines are grouped by processor speeds such as 1 to 2 GHz and 2 to 3 GHz processors. You can see which devices are running at or near capacity by expanding the Processor Speed items in the report. Run the Memory Summary report using the same filter. Notice that this report also categorizes the devices by capacity, such as 512 MB to 1 GB and over 1 GB. Once again, expand items in the report to view the devices in a particular category and determine which devices are running at or near capacity. Run the Disk Usage Summary report using the same filter. This report shows devices categorized by Disk Capacity and will quickly show you which devices are running out of hard disk space.
3.
4. 5.
6. 7.
Chapter 6
45
Managing Application Rollout

During deployment of new applications, a project manager needs to progress carefully. It is never advisable to simply deploy the app to all desktops without proper testing. It should be a phased approach that includes testing, pilot deployment, partial production deployment and then full deployment. Throughout each phase, the systems should be monitored for stability and performance, ensuring that the eventual full deployment does not have a negative impact on either user productivity or on the corporate network. What methods do we have available to monitor performance and stability during pilot phases? Typically, it has been a manual process of communication with pilot users who report on any perceived issues. In responding to these issues, the project manager may have someone visit the desk and run monitoring tools on that specific system. This process does not provide optimal data and can leave the picture incomplete. EdgeSight provides the capability of evaluating performance and stability across a group of machines over a given period of time. The following scenario demonstrates how EdgeSight can be used to analyze a specific set of machines that are the pilot for a new application. Performance and stability can be evaluated before, during and after the deployment of the application, allowing you to make an informed decision about the impact on the environment.
Application Rollout Scenario

John is the project manager for the deployment of a new Line of Business (LOB) application. In a labratory situation, he tested the application on corporate Windows XP builds and has seen that the application behaves well with other corporate applications. It is now time to deploy the application to a group of 50 pilot users who constitute a representative sample of the companys job functions. The goal is to ensure that the application does not adversely affect system performance or stability during the course of a regular work day. John plan is to perform the following tasks: From a central location, monitor the CPU and memory of the pilot machines after deployment of the new application Compare this performance to what it was before the deployment
From a central location, monitor the stability of the pilot machines after the deployment of the new application Compare this stability to what it was before the deployment Gather specific error messages or other data related to instability in order to solve the issues.
46
EdgeSight collects all the data that John is planning to use in his evaluation. The historical performance and stability metrics are already there for his pilot machines and EdgeSight will continue to gather this data throughout the duration of the pilot. John now needs to organize the data and generate the right reports to meet his needs. Start by creating a filter group that contains all of the machines in the pilot. This can be done by either creating a query based group that automatically places any machine with the LOB application installed into the group, or by manually adding the machine names to the group.
Note You will require the Edit Public Groups premission in order to create a new group or edit an existing group.
Using the Memory Summary report, show average memory usage for the group before the deployment of the application and then again to show average memory usage for the time period after deployment. Using the CPU Summary report, show average CPU usage for the group before the deployment of the application and then again to show average CPU usage for the time period after deployment. Using the Alerts for a Group by Device report, show alerts generated from the group during a time period before deployment and then again for the time period after deployment.
Creating a Group for Pilot Machines

The first step in managing the application rollout is determining which machines will participate in the pilot and grouping those machines together for ease of reporting. 1. 2. 3. 4. Navigate to Company Settings > Server > Device Management > Groups. In the right-hand pane, where the list of existing groups appears, click New Group. In the New Group dialogue that appears, choose a descriptive name for the group. Choose how long this group will exist on EdgeSight Server using the Expires After drop down menu. You should choose a setting which will encompass the pilot project time frame. The Refresh this group capabilty lets you specify how often a query-based group will run its query to update membership. This does not apply to static lists of machine names.
5.
Chapter 6
47
6. 7. 8. 9.
Choose whether you want to make this group available to other EdgeSight console users or make it only visible to yourself. Select the Take me to the Add Members Page checkbox and click OK Create the Group. On the Edit Members page, choose Devices in order to add members to the group by their names. On the Edit Device Members page, you have several options for choosing devices. If all device names that you want exist in a text file you can import that list by choosing Import File at the top of the page. Otherwise, you will need to either browse for the names by entering information in the Department and Filter fields and clicking Go or by typing each name in the Device field and clicking Add Member.
10. 11.
Click Next and then Finish to create the group. After completing the group creation, your new group will now appear as an option when filtering reports anywhere within the EdgeSight console.
Displaying Current and Prior Memory Usage

The next step is to display the average memory usage for the group before and after the deployment. 1. 2. 3. Navigate to Device > Performance and go to the specific report list for the resource (CPU or Memory). Run the CPU Summary and the Memory Summary reports. In the filter box at the top of the page, select the Group radio button and then from the drop-down box choose the pilot group that you created. Select a date range that is from the point of deployment onward. To see memory or CPU usage before deployment, run the report again with a date range that starts and ends before deployment of the new app. The results will categorize machines by their capacity: processor speed or physical memory, depending on the report.
4.
Displaying Prior and Current Alerts

In order to gauge the stability of the application, you can display alerts generated by the group before and after deployment. 1. 2. 3. Navigate to Real Time > Alerts > Alert Reports. Run the Alerts for a Group by Device report. In the filter box at the top of the page, select the Group radio button and then from the drop-down box choose the pilot group that you created.
48
Select a date range that is from the point of deployment onward. To see alerts generated before deployment, run the report again with a date range that starts and ends before deployment of the new app. 4. 5. The results show the alert count for each machine in the group for the given date range. Expand the row associated with a machine name to view actual alert messages and times.
Managing Multiple Application Versions

Multiple versions of applications can be difficult to track down in a large client environment. Issues can be specific to a particular version of the application and so it becomes necessary to determine the version running on a users machine when trying to troubleshoot problems. EdgeSight allows you to determine application versions without visiting the users machine or displaying their registry. Also, EdgeSight allows you to compare historical performance and stability between different versions running in the environment.
Multiple Application Version Scenario

A user calls complaining about a particular application. The performance seems slow and it crashes periodically. Knowing that issues existed with prior versions of the application, the support person wants to quickly determine which version is running on the users machine. If it is not the latest, then the easy fix is to upgrade the application. However, if it is the latest, then the support person may want to compare the performance and stability of this machine with other machines running the same version of the application. EdgeSight contains information about all applications that have run in the environment, including version numbers. There are a number of ways to find what version of an application is running on a users machine. The following ar two of the most direct ways to display application versions: Navigate to Real Time > Remote > Processes, specify the device, and display the Properties of the process. This will tell you, among other things, the current version number. If the process is not currently running, you can navigate to Devices > Configuration and run the New Processes for a Device report. You may need to adjust the timeline to include the application in question.
Chapter 6
49
To find other machines running the same version of an application, do the following: Navigate to Processes > Licensing & Utilization and run the Usage for a Process by Day report. To run the report, you will need to filter to show only the process you are interested in and only the specific version of the process. Another useful report, located on the same report list, is the Usage for a Category by Day. This allows you to expand a day and display all versions running of the application. You can click on a specific version number and then display the Usage for a Process by Day reports for that application and version.
Displaying the Process Version

Find the version number of a running process: 1. 2. 3. 4. Navigate to Real Time > Remote > Processes. Browse for the name of the target machine in order to populate the Device field. The page displays a list of all processes currently running on the target machine. Find the process you are interested in, click the menu icon, and select Properties. The resulting information includes the version number:
Displaying Machines Running the Same Process Version

To find other machines that are running the same app version: 1. 2. 3. Navigate to Processes > Licensing & Utilization > Usage for a Process by Day. Choose the date range and click on the selection icon to choose a process. In the Process Picker, select the Show Version checkbox and click Filter. This adds a version column to the result set. Picking a process without this selection will search for all versions of the process. Find and choose the version of the application you are searching for and click OK. Then click the Go button to search for machines that are using this version of the application. Given this information, you can start to compare performance and stability of these machines.
4.
5.
50
Managing Licensing and Compliance

Every year, software vendors conduct a true up with their clients; a process used to license new and incremental PCs above the initial volume license agreement. In large organizations, it can be difficult to control the installed base of applications and the dollar amount owed to the software vendor can be significant. While there are many ways of determining where an application is installed, it is typically not so easy to determine which of those instances of the process is actually being used. Many of them may have been installed initially for a particular user and then that user decides he does not need it after all; or the user moves to another machine and the application does not get removed from the old machine. Using EdgeSight, you can determine which installations of an application are actually being used and which are not. Armed with this information, you can uninstall the application from all desktops where the application is not being used. This process will help keep you in compliance with your volume license agreements.
Licensing and Compliance Scenario

Joan is responsible for licensing and compliance at a financial firm that has 6000 users. They have a volume license for 500 installations of a stock trading application called TraderApp. The software vendor for TraderApp is due for its annual audit of the install base, and Joan knows there have been quite a few extra, unused installations of the application. Using their software deployment tools she currently sees 700 installations in total. The extra 200 will cost her firm a significant amount of money. She wants to evaluate which installations are not being used so she can have them uninstalled. Joan wants to accomplish the following: Generate a report showing all machines where TraderApp has been used during the last quarter. Generate another report showing all machines where the application has been used during the last month. Compare these reports to the installed base to determine which machines have not run TraderApp during the last quarter and which machines have not run it for at least the last month. Use software deployment tools to uninstall the application from some machines and get back into compliance with their volume license agreement.
Chapter 6
51
EdgeSight maintains application usage data. This data can be archived over the course of the year so reports will be easily accessible. To display the required application usage information: Use the Usage for a Process by Day report to show all usage of a particular version of an application during the course of a quarter or month. Use the Usage for a Category by Day report to see all the usage of a particular category or set of applications during the course of a quarter or month.
Note These reports can be generated for any time frame for which data is available. A quarter and a month are used for the sake of this scenario partly because the default is to groom process usage data after 90 days.
Displaying Application Usage

View the usage of a particular process for a given time frame: 1. 2. 3. 4. 5. Navigate to Processes > Licensing & Utilization > Usage for a Process by Day. Choose a time frame within which you would like to view usage data. Select the process you want by clicking the selection icon and finding the process using the Process Picker. Click OK. Click Go to generate the report according to the selected parameters. The report displays both Active Time and Running Time. Active Time tells you how long the application was in the forefront. Running Time tells you the total time the application was in memory. Expand a report row to show which devices were running the application on that day.
6.
52
C HAPTER 7
This chapter provides guidelines for transferring Citrix EdgeSight data to long term storage for using in analysis and recordkeeping. Archiving and warehousing data provides continued access to large amounts of data while ensuring optimum performance from your Citrix EdgeSight server.
Archiving Data
This section describes how to archive Citrix EdgeSight data for use in long-term reporting and record keeping. Citrix EdgeSight collects a wide range of performance, availability, and usage data about end-user systems, applications, and the network. Citrix EdgeSight Agents collect data from end-user systems or Citrix Presentation Servers and upload it to a Citrix EdgeSight Server. On the server, it is stored in a database which serves as the data source for a report server. Because of the large amounts of data collected, data is groomed from the database after a configurable number of days, depending on the type of data. Data required for long-term use, such as trend analysis, compliance documentation, and capacity planning, should be archived in preference to relaxing the grooming configuration. Data archiving ensures that required data is available for long-term reporting without compromising the performance of Citrix EdgeSight in day-to-day operations. Archived data can serve a number of purposes. For example, Citrix EdgeSight tracks application usage for use in calculating how long an application is active, collecting active tasks and applications for crash reports, and usage counts for license tracking. Archived application usage data can be used as follows: document compliance with license agreements plan application license purchases provide data for use in software audits and compliance programs
54
Note Depending on your reporting needs and the data retention policies of your enterprise, you may want to consider data warehousing. See Warehousing Citrix EdgeSight Data for more information on defining a data warehousing strategy.
Defining Archive Requirements

There are a number of considerations to be taken into account when planning your data archive: What data needs to be archived?Determine what reporting and analysis is to be performed on the data. Once requirements are defined, relevant data can be specified. How frequently does data need to be archived?Determine how often application usage data is groomed from the production database. Report archiving schedules must take into account the grooming schedule to avoid introducing gaps in data. How much data storage is required?Determine how much the selected data contributes to the daily growth of the archive.
Selecting Data for Archiving

Data should be selected for archiving based on a specific and repeatable business need. For example, memory and CPU usage data is critical for analyzing trends used in capacity planning. Application usage data is required for some license compliance records. Some data, such as that stored for incoming real-time alerts, has little relevance past the immediate problem response time. Historical alert data, those alerts collected by the agent and uploaded daily, is stored in a separate table and is more relevant for the analysis of problem trends.
Chapter 7
55
Once the required data is identified, use the SQL views to select the individual data items to be warehoused. (For a complete description of the views, see the Accessible SQL Views topics in the EdgeSight Server Online Help.) Use the inserted_date field in a SQL view to select records inserted after a specific date and time. (This feature was introduced as of EdgeSight 4.1.) SQL views provide both stability and ease of use, as compared to selecting data based on the database schema. While the underlying database schema may change, Reflectent will make every effort to only extend the views by the addition of columns. When selecting data based on views, it is best practice to select the specific columns you want to archive. When writing SQL scripts for archiving EdgeSight data, do not use a statement with SELECT *. As the views are extended, this could cause the script to fail. By selecting specific columns, you avoid problems if columns are added to views at a later date. Citrix EdgeSight provides the following views intended for use in archiving: Citrix EdgeSight for Endpoints views Alert archive Incoming alert archive Application performance archive Application usage archive Application network performance archive Application network transactions performance archive Drive space archive Light trace event archive System performance archive Asset summary archive Asset detail archive
Citrix EdgeSight for Presentation Server views Client startup performance archive Environmental usage archive ICA roundtrip performance archive Server startup performance archive System performance for a device System performance for a session
56
Determine Archiving Frequency

The frequency with which you choose to archive data will be determined by the data selected and the grooming schedules for data of that type. To prevent data loss, the archiving frequency should be less than the shortest grooming parameter. Note that the grooming parameters are configurable and may be different in your environment. To display the current grooming schedules for EdgeSight data along with the views associated with each data type, navigate to Server Settings > Maintenance > Grooming > Configuration. Once you have defined the set of data that need to be archived, you can determine how much data storage is required. The size of the production database can vary greatly depending on the number of managed devices, the number of applications running, and the number of network transactions performed. The first step to determining the storage required for the archive is the average amount of data collected over a specific time period. This allows you to estimate the amount of data collected for longer periods. Another factor to consider is how long data is to be maintained in the archive. To manage the size of the archive, define a grooming strategy or transfer data (or a subset of the data) to a long-term archive at scheduled intervals.
Warehousing Citrix EdgeSight Data

This section includes information about designing a strategy for warehousing historical data collected by Citrix EdgeSight. Once warehoused, data can be used for reporting on and analyzing long-term trends and performing capacity planning. This information is meant to be used in conjunction with the documentation for your data warehouse system. Citrix EdgeSight collects a wide range of performance, availability, and usage data about end-user systems, applications, and the network. Citrix EdgeSight Agents collect data from end-user systems and upload it to a Citrix EdgeSight Server. On the server, it is stored in a database which serves as the data source for a report server. Because of the large amounts of data collected, data is groomed from the database after a configurable number of days, depending on the type of data. Database grooming is critical for maintaining optimum server performance. Although database size is subject to multiple factors (the number of agents, the number of processes, the amount of network traffic, and the data collection hours), the grooming schedule allows administrators to effectively control database size. Data required for long-term use, such as trend analysis, compliance documentation, and capacity planning, should be warehoused in preference to relaxing the grooming configuration. Data warehousing ensures that required data is available for long-term reporting without compromising the performance of Citrix EdgeSight in day-to-day operations.
Chapter 7
57
Data Warehousing Components

The warehousing architecture for Citrix EdgeSight data includes the following components: Citrix EdgeSight production databaseProvides storage for current performance and availability data and for alerts. Data is subject to regular grooming. The database resides on the production Citrix EdgeSight Server. Data transfer mechanismTools used to transfer data from the production database to the data warehouse. These tools may include, but are not limited to, SQL Server Data Transformation Services (DTS) for SQL Server 2000, SQL Server Integration Services (SIS) for SQL Server 2005, or custom SQL scripts. Note that SIS is a component of SQL Server 2005 that provides all basic ETL (extract, transform, and load) capabilities as well as advanced integration and data transformation functions. SIS is also well integrated with Reporting Services. The optimum tool will depend on your environment and the type of data warehouse. Data warehouseProvides storage for historical data used in long-term reporting and analysis.
Note For a less formal and more lightweight approach to data retention, consider using archive reports as a means of storing data, as described in Using Archive Reports to Warehouse Data on page 60.
The production server should be on a dedicated server with the warehouse database on a separate server. The report server used to create reports from the data warehouse can either be on the same server with the warehouse database, or on a separate server. The following figure shows the components involved in the data warehousing solution.
58
Citrix EdgeSight Data Warehousing Strategy

There are a number of considerations to be taken into account when planning your data warehouse: What data needs to be warehoused? Determine what reporting and analysis is to be performed on Citrix EdgeSight data. How frequently does data need to be warehoused?Determine what data is selected for warehousing and how often that type of data is groomed from the production database. How much data storage is required?Determine what data is selected for warehousing and how much this data contributes to the daily growth of the production database. What operations will be performed on the data?Determine how the data will be used. If data analysis is to be performed, storage in a database is required. If data is stored for recordkeeping purposes only, it may be sufficient to archive reports to a file share as CSV files. Reports can be loaded into a database as required.
Chapter 7
59
Select Data for Warehousing

Data should be selected for warehousing based on a specific and repeatable business need. For example, memory and CPU usage data is critical for analyzing trends used in capacity planning. Application usage data is required for some license compliance records. Some data, such as that stored for incoming real-time alerts, has little relevance past the immediate problem response time. Historical alert data, those alerts collected by the agent and uploaded daily, is stored in a separate table and is more relevant for the analysis of problem trends. Once the required data is identified, use the accessible SQL views provided by Citrix EdgeSight to select the individual data items to be warehoused. (For a complete description of the views, see the Accessible EdgeSight SQL Views and Accessible Citrix SQL Views topics in the Citrix EdgeSight Server Online Help.) The views provide both stability and ease of use, as compared to selecting data based on the database schema. While the underlying database schema may change, every effort will be made to only extend the views by the addition of columns. The views intended for use in data warehousing: are the same as those intended for archiving, as listed in Selecting Data for Archiving on page 54. When selecting data based on views, it is best practice to select the specific columns you want to warehouse. When writing SQL scripts for warehousing Citrix EdgeSight data, do not use a statement with SELECT *. As the views are extended, this could cause the script to fail. By selecting specific columns, you avoid problems if columns are added to views at a later date.
Determine Warehousing Frequency

The frequency with which you choose to transfer data to the warehouse will be determined by the data selected and the grooming schedules for data of that type. To prevent data loss, the warehousing frequency should be less than the shortest grooming parameter. Note that the grooming parameters are configurable and may be different in your environment. See Determine Archiving Frequency for the default grooming schedules for Citrix EdgeSight data along with the views associated with each data type.
60
Determine Data Storage and Disk Configuration Needs

Once you have defined the set of data that need to be warehoused, you can determine how much data storage is required. The size of the production database can vary greatly depending on the number of managed devices, the number of applications running, and the number of network transactions performed. The first step to determining the storage required for the data warehouse is the average amount of data collected over a specific time period. This allows you to estimate the amount of data collected for longer periods. Another factor to consider is how long data is to be maintained in the warehouse. To manage the size of the data warehouse, define a grooming strategy or transfer the database (or a subset of the data) to a long-term warehouse at scheduled intervals.
Using Archive Reports to Warehouse Data

Citrix EdgeSight provides a number of archive reports based on the accessible SQL views. As an alternative method of data warehousing, you can regularly export selected reports to a CSV (comma delimited) format and archive the reports on a file share. The CSV files can be loaded into a database as required for later use. This is an effective means of retaining data which is required for record keeping, such as usage or compliance data, but is not used for analysis. Standard archive reports can be used as templates for the creation of custom reports which contain only the data required for retention. This can help reduce the overall size of the stored data.
61
Index
A
ActiveX Control 15 administrative privileges 15, 34 application using EdgeSight to manage rollout 45 applications using EdgeSight to manage versions 48
N
network delay comparing current and historical 39 comparing devices 39 network problems resolving 37 network round trip time 29 network volume identifying 40
C
capacity planning using EdgeSight to manage 43 client session startup time 29 compliance using EdgeSight to manage 50 Configuration Check worker 15 crash reports 35
P
Presentation Server Session Wizard 30
R
real time reports 15 Related Reports 14 remote reports 15 reports historical 14 real time 15 related 14 remote 15 resource usage displaying 44 round trip time (RTT) 28 RTT See round trip time
D
Data Upload worker 15
H
hardware asset changes 34 historical reports 14
I
ICA round trip time 29 ICA session latency 28
L
licensing using EdgeSight to manage application licenses 50
S
SEMS See session experience monitoring server session startup time 29 session experience monitoring 28 session performance 27 software asset changes 34 Support Wizard 14
M
memory usage displaying 47
62
T
Trace Route 40
W
worker Configuration Check 15

EdgeSight User Guide

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

EdgeSight User Guide

Încărcat de

Drepturi de autor:

Formate disponibile

Citrix EdgeSight Users Guide

Using Citrix EdgeSight Reports

Using EdgeSight to Resolve System Performance Problems

Citrix EdgeSight Users Guide

Using EdgeSight to Resolve Session Performance Problems

Using Citrix EdgeSight to Resolve Applications Problems

Using Citrix EdgeSight to Resolve Network Problems

Using Citrix EdgeSight for Planning and Implementation

Citrix EdgeSight Users Guide

Using Citrix EdgeSight Data for Analysis and Recordkeeping

Citrix EdgeSight Users Guide

Before You Begin

Citrix EdgeSight Users Guide

Implementing Solutions with EdgeSight

Resolve System Performance Problems

Resolve Application Problems

Resolve Network Problems

Proactively Manage Hardware and Software Assets

Capture and Store Data for Long Term Use

Citrix EdgeSight Users Guide

Using Citrix EdgeSight Reports

Citrix EdgeSight Users Guide

Citrix EdgeSight Server Console

Using Citrix EdgeSight Reports

Citrix EdgeSight Users Guide

Accessing and Using Historical Reports

Finding Reports Using the Support Wizard

Finding Related Reports

Using Citrix EdgeSight Reports

Accessing and Using Remote Data

Using Real-Time Reports

Citrix EdgeSight Users Guide

Using Citrix EdgeSight Reports

Real-Time Report Components

Citrix EdgeSight Users Guide

Displaying Real-Time Reports

Using Citrix EdgeSight Reports

Process performance on the selected device

Presentation Server User Summary

Citrix EdgeSight Users Guide

Accessing and Using Real Time Alerts

Accessing and Using Process Fault Data

Using Citrix EdgeSight Reports

Capturing Context at the Onset of a Performance Problem

Citrix EdgeSight Users Guide

Using EdgeSight to Resolve System Performance Problems

System Performance Scenario

Citrix EdgeSight Users Guide

Use the Performance Summary for a Device report to display

charts on CPU, memory, page fault, and disk space.

Using EdgeSight to Resolve System Performance Problems

Displaying Recent Alerts

Displaying the Historical Performance for a Device

Citrix EdgeSight Users Guide

Display Asset Changes

Display Resource Utilization Information

Using EdgeSight to Resolve Session Performance Problems

Session Performance Scenario

EdgeSight provides session performance data in historical reports, including

Citrix EdgeSight Users Guide

Displaying Session Latency Data

Displaying Round Trip Time Data

Using EdgeSight to Resolve Session Performance Problems