Importance of Monitoring Citrix Logon Performance Citrix logon time refers to the amount of time it takes from the moment a user clicks on an application or desktop icon to the time when the application or desktop shell appears. Diagnosing Citrix logon slowness has always been a challenge in Citrix infrastructures. In the 2016 Citrix. This article details the performance counters and event viewer messages that can be used to gauge the health of a XenApp farm’s infrastructure components. The primary goal of this document is to provide a list of identifiers which are typically associated with a problem that is highly likely to prevent or degrade the performance of application enumeration and/or launch. A while ago I wrote some monitoring software to get a high level view of whats happening on your Citrix XenApp 6.5 Estate. Details of this can be found here: XenApp 6.5 Monitoring Tool I have had.
- Monitoring Xml Service All About Citrix Access
- Monitoring Xml Service All About Citrix App
- Monitoring Xml Service All About Citrix Password
- Monitoring Xml Service All About Citrix Client
This post has already been read 22582 times!
A while ago I wrote some monitoring software to get a high level view of whats happening on your Citrix XenApp 6.5 Estate. Details of this can be found here:
I have had loads of requests to update this to support XenDesktop 7.x and to be honest its something I have wanted to do for quite some time but have just not got round to it. This post will offer the first cut in my new monitoring “dashboard”
Just to be clear, this is NOT meant to replace existing monitoring software from vendors like ControlUp etc as the monitoring and specific detail around the Citrix stack they offer is far beyond what I am trying to achieve with this. It IS however meant to be a supplementary piece of monitoring that can be run and used for free and displayed without a login on a large monitoring wallboard or something like that.
The idea is to give you a high level snapshot of the estate when you walk into your workplace.
Some Detail
- The script is written in Powershell and I want to cover more than just the worker servers in this edition – more on that later
- I am NOT a Powershell expert and don’t claim to be. Therefore the code may not be optimised or written to best practice but It should do what it says on the tin and monitor the high level status of your critical Citrix XenDesktop Infrastructure.
- The XenServer Tests use the XenServer SDK – Make sure that this is downloaded and installed before you attempt to test your XenServers. The SDK can be found here
- The Graph used Google Charts so your Web Server that displays the output web page will need internet connectivity
- This IS a community project and is FREE. If you see this being offered at a cost then please let me know. Also – if you want to help, let me know. I already have my first fellow CTP offering to help – Thanks @msandbu
What I want to cover (eventually)
Once this is finished I want to be able to monitor the below. You may ask why release it early? The reason is it will give me the kick in the butt to finish this as it will be “out there”
- Citrix Licensing – Server Status and Vendor Daemon Port Test
- XenServer – Pool and Host Status and Management Port
- StoreFront – Server Status, Protocol Port and Receiver For Web Response Code
- NetScaler – Appliance Status and vServer Status (Up, Down, Degraded)
- Provisioning Services (TBA)
- Citrix Director (TBA)
- Citrix Brokers (TBA)
- Citrix Ticketing (TBA)
- XenDesktop Session Based Hosts (TBA)
- XenDesktop Desktop VDA’s (TBA)
- NetScaler – Unified Gateway, Content Switching, GSLB Service Status (TBA)
- XenServer – VM Status, Storage Status (TBA)
- Hypervisors – Include Nutanix, VMware and HyperV
So, as you can see there is quite a bit I want to get covered and it will take some time to get written. Like I said, If you want to help drop me an e-mail on dave@bretty.me.uk and I will get you involved. The structure of the files is done in suck a way that it will be easy to collaborate!
What Does It Look Like?
I have built in the ability to customise the web page within reason, but more about this later in the post. The reason for using a bar chart as opposed to a donut chart this time is that it gives the ability to scale out the monitoring areas without having to re-write the web generating code.
How Does It Work?
Like I said earlier, it is all Powershell driven. To get it up and running is pretty straight forward. You just get the scripts and registry file, set up the required directory structure and registry values and trigger the main PS1 file using a scheduled task as often as you want the monitor to run.
Installing The Software
First, you will need to monitoring server to run the script from. You can use one of your StoreFront Servers for this if you require or build a new one, will leave that up to you. In my lab I am running this from my Domain Controller.
NOTE: If you want to monitor XenServer you will need to install the XenServer SDK as mentioned earlier.
Set Up The Registry
E-mail me and request the link to the monitoring files. Extract the files and import the monitoring_registry.reg file into the registry of your monitoring server.
It will create all the values for this version of the script under a key “HKLMSoftwarebretty.me.ukmonitoring”
As you will see below there are quite a few values in there, I will run through what all of them are used for.
- CitrixLogo – File name for the Citrix Logo Displayed in the upper left hand part of the web page (needs to be in the same location as the outputted web page)
- ColumnBad – RGB Code for showing services as down (Include the #)
- ColumnGood – RGB Code for showing services as up (Include the #)
- CompanyLogo – File name for your company logo – displayed in the upper right of the web page (needs to be in the same location as the outputted web page)
- GraphHeight – Height of the Google Chart
- GraphWidth – Width of the Google Chart
- LicenseServers – Comma delimited list of your license servers
- LicensingTitle – Title for the Licensing part of the Google Chart
- LicensingVendowDaemonPort – Vendor Daemon Port you run licensing on
- LogError – Full Path to Error Log File
- LogHTML – Full Path to HTML Data used to load Google Chart
- LogHTMLOut – Full Path to HTML Output File
- LogVerbose – Full Path to Verbose Log File
- NetScalers – Comma delimited list fo NetScalers
- NetScalerTitle – Title for NetScaler Part of Google Chart
- NetScalervServerTitle – Title for NetScaler vServer Part of Google Chart
- NSPassword – NetScaler Password used for connection
- NSUserName – Username used for NetScaler Connection
- StoreFrontPort – Port you run Citrix StoreFront on
- StoreFrontProtocol – http or https
- StoreFrontServers – Servers that you use to run StoreFront
- StoreFrontTitle – Title for the StoreFront part of the Google Chart
- StorePath – Path to Receiver for Web Site (include initial /)
- TestLicensing – (yes/no) Do you want to test Citrix Licensing
- TestNetScaler – (yes/no) Do you want to test NetScaler and the vServers
- TestStoreFront – (yes/no) Do you want to test StoreFront
- TestXenServer – (yes/no) Do you want to test Citrix XenServer
- XenPassword – Password for your XenServer Pool Masters
- XenPoolMasters – Comma delimited list of XenServer Pool Masters
- XenServerHostTitle – Title for XenServer HOST part of Google Chart
- XenServerManagementPort – Management Port used for XenServer Connections
- XenServerPoolTitle – Title for XenServer POOL part of Google Chart
- XenUserName – Username used to conencto to your XenServer Pool Masters
Once you have your registry configured it should look similar to the below
Set Up The Scripts
Also you will find a scripts directory.
Extract that and put it in the root of your monitoring server. The folder will contain a few ps1 files, here is what they are all for.
- monitor.ps1 – the main script file and the one that you will execute to perform the monitoring
- build-html.ps1 – used to build the output web file
- global.ps1 – all global functions used across multiple monitoring modules
- licensing.ps1 – Licensing Monitoring Module
- netscaler-vserver.ps1 – NetScaler vServer Monitoring Module
- storefront.ps1 – StoreFront Monitoring Module
- xenserver.ps1 – XenServer Monitoring Module
Once extracted you will see the scripts locally on your monitoring server.
NOTE: Make sure the jpg files you specified in your registry config are in the same location as your output html file. In my case I’m going to put the output in the Scripts Directory.
Running The Script
At this point you are ready to test run the script. Open up Powershell (With XenServer SDK Installed if your monitoring XenServer) and run the master script.
You will see the script executing and a verbose output on the Powershell display
Once the script has completed you will see the following in your Powershell window
If you look in your output directory you will see the log files and the html output file. Lets open that up and see what we have
As you can see Its picked up my License Server and tested the Vendor Daemon port as ok, My XenServer Pool is good and the 2 hosts are running, StoreFront and the BrettyWeb Store is up and finally my NetScaler is working and all 12 vServer are up and not Degraded.
Lets Bring some stuff down to make sure it shows this on the dashboard
Firstly I have disabled my ADFS Server so the ADFS vServer is down. I have also added a dummy entry to my StoreFront vServer so that it is only partially up
I have also shut down one of my XenServers in my Lab Pool
So, lets re-run the monitoring script
As you can see it has picked up on some services down. Lets have a look at the monitoring screen now
As you can see its picked up that my XenServer Pool is still ok but one of the hosts is now down. It has also marked on of my vServers as DOWN and alerted on another as degraded but left the service as up.
Getting the Software
Simple – Just drop me an e-mail and I will send you a ShareFile link to the software and scripts. The reason I am asking you to give me your e-mail address is so that I can update and send the scripts as and when they change directly to you, for free. That will keep you up to date and with the latest script files with no hassle on your part.
UPDATE – Added Citrix Director and Citrix Workspace Environment Management to the scripts. As part of the initial download and install you will now get Director and CWEM – for details of the registry keys and whet they do see this article.
Thats it, release one is out there. Better get going with release 2.
Laters,
b@m
Overview
Virtual Apps (formerly XenApp) is Citrix's solution for application and desktop delivery, with over 100 million users worldwide. Citrix Virtual Apps extends Microsoft Remote Desktop Sessions and applications to users through the Citrix HDX protocol, enabling secure, remote access to Windows applications and server desktops from any device, over any network.
Applications Manager helps quickly drill down to the root cause of a problem in Citrix Virtual Apps and resolve slowness in an application running on a Citrix Virtual Apps server. You can track the performance of Broker Services, client and server sessions and diagnose issues like server overload using event logs.
Creating a new monitor
Supported versions of Citrix Virtual Apps Server: Citrix Virtual Apps 7.6 and 6.5
Prerequisites for adding the monitor: You should have .NET 3.5 framework installed in Applications Manager.
Applications Manager connect with Citrix Virtual Apps Server and used to determine the Performance of various services and components of Citrix Virtual Apps Server. Follow the steps given below to create a new Citrix Virtual Apps monitor:
Monitoring Xml Service All About Citrix Access
- Click on New Monitor link.
- Select Citrix Virtual Apps under Virtualization category.
- Specify the Display Name of the Citrix Virtual Apps Server.
- Enter the Host Name (Delivery Controller) or IP Address of the host where the Citrix Virtual Apps server runs.
- Select the Version number from the drop-down menu.
- If you choose the Use Below Credentials option, then enter the credentials - UserName and Password of the Citrix Virtual Apps Server Host Machine. UserName- Name of the User who has the permission to execute WMI Queries for the respective Versions on the following namespaces in Delivery Controller machine.
NameSpaces For Version 7.6:
Password - Password of the above user who has the permissions to execute WMI Queries. If you choose the Select from credential list option, then select the respective credential from preconfigured credential list.- rootcimv2
- rootcitrixeuem
- rootcitrixprofilesmetrics
- rootcimv2
- rootcitrix
- Select Enable Event Log Monitoring if you wish to monitor event logs.
- Specify the Polling Interval in minutes.
- Choose the Monitor Group with which you want to associate the Citrix Virtual Apps to, from the combo box (optional). You can choose multiple groups to associate your monitor.
- Click Add Monitor(s). This discovers the Citrix Virtual Apps from the network and starts monitoring it.
Monitored Parameters
Go to the Monitors Category View by clicking the Monitors tab. Click on Citrix Virtual Apps under the Virtualization Table. Displayed is the Citrix Virtual Apps bulk configuration view distributed into three tabs:
- Availability tab, gives the Availability history for the past 24 hours or 30 days.
- Performance tab gives the Health Status and events for the past 24 hours or 30 days.
- List view enables you to perform bulk admin configurations.
Click on the tabs listed below to view the corresponding metrics monitored for different versions of Citrix Virtual Apps:
| Citrix Virtual Apps Version 7.6 | Citrix Virtual Apps Version 6.5 |
Monitored Parameters for Citrix Virtual Apps Version 7.6
Performance Overview
| Parameter | Description |
|---|---|
| Performance of Broker Services | |
| Average Transaction Time (in Seconds) | The time on average taken to process an XML transaction in Citrix Broker Service. |
| Concurrent Transactions | The number of concurrent XML transactions being processed in the Broker Service. |
| Transactions/Sec | The number of XML transactions being processed per second. |
| Services | |
| Service Name | The name of the service. Note that the display name and the service name (which is stored in the registry) are not always the same. |
| Start Mode | The Start mode of the service. The different start modes are:
|
| Status | The current status of the object. Both operational and nonoperational statuses can be defined. Operational statuses include: 'OK', 'Degraded', and 'Pred Fail' etc. Non-operational statuses include: 'Error', 'Starting', 'Stopping', and 'Service' etc. |
| State | The current state of the base service. Possible values are:
|
End User Experience
| Parameter | Description |
|---|---|
| Server Session Start-Up Durations | |
| Session ID | The unique ID for each user session. |
| Client IP | The IP address of the device connecting to a Citrix Virtual Apps / Presentation Server. |
| Client Machine Name | The name of a device connecting to a Citrix Virtual Apps / Presentation Server. |
| Logon Client User Name | The name of the user who is connecting to the Citrix Virtual Apps / Presentation Server and accessing published application. |
| Credentials Authentication (in ms) | The Credentials Authentication Server Duration (CASD) is the time the application server spends authenticating the user's credentials against the authentication provider, which may be Kerberos, Active Directory, or a Security Support Provider Interface. |
| Credentials Obtention (in ms) | The Credentials Obtention Server Duration (COSD) is the time taken for the server to obtain the user credentials. Because this metric may be artificially inflated if a user fails to provide credentials in a timely manner, it is not included in the Session Start-up Server Duration (SSD). |
| Drive Mapping (in ms) | The Drive Mapping Server Duration (DMSD) is the time needed for the server to map the user's client drives, devices and ports. |
| Printer Creation (in ms) | The Printer Creation Server Duration (PCSD) is the time required for the server to synchronously map the user’s client printers. If the configuration is set such that printer creation is performed asynchronously, no value is recorded for PCSD as it is does not impact completion of the session start-up. |
| Profile Load (in ms) | The Profile Load Server Duration (PLSD) is the time required for the server to load the user’s profile. |
| Session Creation (in ms) | The Session Creation Server Duration (SCSD) is the time the server spends creating the session. This should not be confused with the overall SSD. |
| Session Startup (in ms) | The Session Startup Server Duration (SSSD) is the high-level server-side connection start-up metric that encompasses the time Citrix Virtual Apps takes to perform the entire start-up operation. When an application starts in a shared session, this metric is normally much smaller than when starting a new session, which involves potentially high-cost tasks such as profile loading and login script execution. |
| Client Session Startup Durations | |
| Session ID | The unique ID for each user session. |
| Client IP | The IP address of the device connecting to a Citrix Virtual Apps / Presentation Server. |
| Client Machine Name | The name of a device connecting to a Citrix Virtual Apps / Presentation Server. |
| Logon Client User Name | The name of the user who is connecting to the Citrix Virtual Apps / Presentation Server and accessing published application. |
| Application Name | The name of the application user request to get session. |
| Application Enumeration (in ms) | The Application Enumeration Client Duration measures the time needed to retrieve the list of applications from the Web Interface service. Application enumeration is one of the issues slowing down session start times. |
| Back-Up URL Client Count | The BackUp URL Client Count (BUCC) is a recording of the number of back-up URL retries before a successful launch. This is the only start-up metric that is a measure of attempts, rather than time duration. If this metric has a value higher than 1, it indicates the Web Interface server is unavailable and the Citrix Virtual Apps Plugin (formerly known as Program Neighborhood Agent) is attempting to connect to back-up Web Interface servers to launch the application. |
| Credentials Obtention (in ms) | The Credentials Obtention Client Duration (COCD) is the time it takes to obtain user credentials. Note: COCD is only measured when the credentials are entered manually by the user. Because this metric may be artificially inflated if a user fails to provide credentials in a timely manner, it is subtracted from the Startup Client Duration (SCD). This consideration is especially important if the metric is to be used for threshold alerting. |
| Configuration File Download (in ms) | The Configuration File Download Client Duration (CFDCD) is the time it takes to get the configuration file from the XML server. |
| ICA File Download (in ms) | The ICA File Download Duration (IFDCD) is the time it takes for the plugin (client) to download the ICA file from the server. Note: The overall process involved in downloading the ICA file is:
|
| Launch Page Web Server (in ms) | The Launch Page Web Server Duration (LPWD) metric is only used when Web Interface is the application launch mechanism. If LPWD is slow, there is a bottleneck on the Web Interface server.Process under this:
|
| Session Look-Up (in ms) | The Session Look Up Client Duration (SLCD) represents the time it takes to query every session to host the requested published application. The check is performed on the client to determine whether an existing session can handle the application launch request. The method used depends on whether the session is new or shared. |
| Session Creation (in ms) | The Session Creation Client Duration (SCCD) is the time it takes to create a new session, from the moment wfica32.exe is launched to when the connection is established. |
| Startup Client (in ms) | The Startup Client Duration (SCD) is a high-level client connection startup metric. It starts as close as possible to the time of the request (mouse click) and ends when the ICA connection between the client device and server running the Citrix Virtual Apps / 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. |
Session Performance
| Parameter | Description |
|---|---|
| ICA Sessions Round Trip Metrics | |
| SessionID | The unique ID for each user session. |
| Client IP | The IP address of the device connecting to a Citrix Virtual Apps / Presentation Server. |
| Client Machine Name | The name of a device connecting to a Citrix Virtual Apps / Presentation Server. |
| Logon Client User Name | The name of the user who is connecting to the Citrix Virtual Apps / Presentation Server and accessing published application. |
| Network Latency (in Seconds) | The detected network latency between the Citrix Virtual Apps / Presentation Server Client device and the server running Citrix Virtual Apps / Presentation Server. |
| Round Trip Time (in Seconds) | The time interval measured at the client between the first step (user action) and the last step (graphical response displayed). This metric can be thought of as a measurement of the screen lag that a user experiences while interacting with an application hosted in a session on a server running Citrix Virtual Apps / Presentation Server. |
| Input Bandwidth Available (in bits/sec) | The bandwidth available on the network ( Citrix Virtual Apps / Presentation Server Client to Citrix Virtual Apps / Presentation Server) in bits per second. |
| Output Bandwidth Available (in bits/sec) | The bandwidth available on the network ( Citrix Virtual Apps / Presentation Server to Citrix Virtual Apps / Presentation Server Client) in bits per second. A value of 0 indicates that no data is available. |
| Frame Send Round Trip Duration (in Seconds) | The time from the start of the frame until the completion of sending frame data to the client. |
Profile Server
| Parameter | Description |
|---|---|
| Logon Timings | |
| Session ID | The unique ID for each user session. |
| Time Taken for Loading Profile (in Seconds) | The profile load time for the given session. It is calculated as: Profile Loaded (Time at which the profile finished loading) - Profile Load Start (Time at which the profile started to load). |
| Time Taken for Logon Script Execution (in Seconds) | The logon script execution duration which is displayed in the Director console. It is calculated as: LogonScriptComplete (Time at which Start-up script is completed) + LogonScriptStartup (Start time of the start-up logon) |
| Logoff Timings | |
| Session ID | The unique ID for each user session |
| Time Taken for Processing Registry | The registry processing duration. The registry values for the current user are processed and saved to the profile store. It is calculated as: Registry processing duration = Registry Processing complete (Registry processing finish time) -- Registry Processing Start (Registry processing start time). |
| Time Taken for File System Processing | The time taken for file synchronization and file system processing. It is calculated as: File System Processing = File System Processing complete (File synchronization and related file system processing finish time) - File System Processing Start (File synchronization and related file system processing start time). |
| Time Taken for CPS Processing | The Cross Platform Setting (CPS) processing duration. It is calculated as: Cross Platform Setting (CPS) processing duration = CPS Processing Complete (Cross-platform settings processing finish time) - CPS Processing Start (Cross-platform settings processing start time). |
| Time Taken for Logoff | The logoff processing duration. It is calculated as: Logoff processing duration = Logoff completed (Time at which logoff process finished) - Logoff start (Logoff process start time) |
| Diagnostics | |
| Session ID | The Unique ID for each user session. |
| Network Latency | Users can create their own profiles in Citrix Virtual Apps Server. Whenever a user logs in or logs out from a session, the profile server is used to authenticate the user, to check accessibility of resources for each user etc. The Network Latency metric indicates if the profile server is online or offline. Possible values are:
|
| Disk Usage | The total bytes consumed by the user of this session. |
| Folder Name | The name of the redirected special folder or the name of the profile store folder in the profile store path. |
Event Logs
| Parameter | Description |
|---|---|
| Rule Name | The name of the event log rule |
| Log File Type | The Log File Type - Application, system, security, file replication service, DNS Server or directory service. |
| Source | The Application which created the event. |
| Event Id | The Event ID associated with the Event Log File. |
| Type | The Event Type - Error, Warning, Information or Event of Any Type. In case of Security Events, the types would vary between Success Audit and Failure Audit. |
| User Name | The system component or User account that was running the process which caused the event. |
| Description | A description of the event. |
| Generated Time | The time when the event entry was submitted. |
Monitored Parameters for Citrix Virtual Apps Version 6.5
Performance Overview
| Parameter | Description |
|---|---|
| SERVER DETAILS | |
| Server Name | The name of the Citrix Virtual Apps Server. |
| IP Address | The IP Address of the Citrix Virtual Apps Server. |
| Farm Name | The name of the Farm under which Citrix Virtual Apps Server is Configured. |
| Zone Name> | The name of the Zone to which the Citrix Virtual Apps Server belongs. |
| Zone Ranking | Zone Ranking specifies the ranking of server in the Zone. Possible ranks are Most Preferred, Preferred, Default Preference, Not Preferred and Unknown. |
| Domain Name | The Domain Name of the Citrix Virtual Apps Server. |
| Server Type | The type of the Server - Windows server or not. |
| CITRIX VIRTUAL APPS SERVER PERFORMANCE | |
| DataStore Connection Failure | The number of minutes that the Citrix Virtual Apps server has been disconnected from the data store. Threshold should take into account events such as reboots and scheduled maintenance. |
| Number of XML Threads | The number of threads allocated to service Web-based sessions. |
| Busy XML Threads | The number of XML threads currently being processed. There are 16 worker threads in the Citrix XML Service. A count of 16 or more shows that XML requests are not being processed in a timely manner. |
| Resolution Work Item Queue Ready Count | The number of resolution work items (related to application launches) that are ready to be executed. A value above 0 indicates that requests are being queued while IMA handles other requests. |
| Work Item Queue Ready Count | The number of work items that are ready to be executed. A value above 0 indicates that requests are being queued while IMA handles other requests. This counter should not be over 1 for an extended period of time. |
| Number of Zone Elections | The number of zone elections. This value starts at zero each time the IMA Service starts and is incremented each time a zone election takes place. |
| Zone Elections Triggered | The number of times a server triggers a zone election. |
| Active Sessions | The number of active user sessions. |
| Disconnected Sessions | The number of disconnected user sessions. |
| Total number of Sessions | The total number of user sessions ( active and disconnected). |
| TRACKING CITRIX VIRTUAL APPS GROWTH | |
| Application Resolution Time | The time in milliseconds that a resolution took to complete. This is also the time required to determine the “least-loaded” server during an application launch. |
| Application Enumerations/Sec | The number of non-XML-based enumerations (requests for application lists) per second. |
| Application Resolutions/Sec | The number of resolutions (applicable launch requests) per second. |
| Filtered Application Enumerations/Sec | The number of XML-based enumerations (requests for application lists) per second |
| LICENSE SERVER CONNECTION FAILURE | |
| License Server Performance | The number of minutes that the Citrix Virtual Apps server has been disconnected from the License Server. |
| Average License Check-In Response Time | The average license check-in response time in milliseconds. |
| Average License Check-Out Response Time | The average license check-out response time in milliseconds. |
| Last Recorded License Check-In Response Time | The last recorded license check-in response time in milliseconds |
| Last Recorded License Check-Out Response Time | The last recorded license check-out response time in milliseconds. A value of more than 5000 milliseconds indicates a performance issue at the license server. |
| CPU UTILIZATION | |
| CPU Usage | The percentage of CPU resource consumed by a user at a given time, averaged over a few seconds |
| CPU Entitlement | The percentage of CPU resource that Citrix CPU Utilization Management makes available to a user at a given time |
| CPU Reservation | The percentage of total computer CPU resource reserved for a user, should that user require it |
| CPU Shares | The proportion of CPU resource assigned to a user |
| Long Term CPU Usage | The percentage of CPU resource consumed by a user, averaged over a longer period than the CPU Usage counter |
Services
| Parameter | Description |
|---|---|
| SERVICES | |
| Service Name | Name of the Services in Citrix Virtual Apps |
| Start Mode | Represent the starting mode(like Auto/Manual/Disabled) of the Services |
| State | Represent the state(like Running/Stopped/Paused) of the Services |
Web Interface
| Parameter | Description |
|---|---|
| WEB INTERFACE PERFORMANCE | |
| Service Name | Name of the Services in Citrix Virtual Apps |
| Queued Request Count | The number of requests waiting to be processed |
| Rejected Request Count | The number of requests rejected because the request queue was full |
| TRACKING WEB INTERFACE GROWTH | |
| Request Execution Time | The number of milliseconds that it took to execute the most recent request |
| Current Request Count | The current number of requests, including those that are queued, currently executing, or waiting to be written to the client |
IMA and ICA (Independent Computing Architecture and Independent Management Architecture)
| Parameter | Description |
|---|---|
| CITRIX IMA NETWORKING | |
| Server Name | Name of the Citrix Virtual Apps Server with IMA Service. |
| Network Connections | The number of active IMA network connections to other IMA servers. |
| Bytes Received/Sec | The inbound bytes in bytes per second. |
| Bytes Sent/Sec | The outbound bytes in bytes per second. |
| ICA SESSION STATS | |
| Client Name | The name of the Client connected with Citrix Virtual Apps Server along with it's Session Name. |
| Average of Session's Latency | The average client latency over the lifetime of a session. |
| Deviation in Latency | The difference between the minimum and maximum measured latency values for a session. |
| Input Session Bandwidth (bits/sec) | The bandwidth, measured in bits per second, used from client to server for a session. |
| Output Session Bandwidth (bits/sec) | The bandwidth, measured in bits per second, used from server to client for a session. |
| ICA ROUND TRIP LATENCY | |
| Median of ICA Round Trip Latency | The median time of ICA roundtrip latency for all sessions on the server. |
Zones and Servers
| Parameter | Description |
|---|---|
| ZONE STATS | |
| Zone Name | The name of the Zone to which Citrix Virtual Apps Server belongs. |
| Data Collector | The one Server in a Zone is elected as the data collector for the other servers. |
| Number of Servers | The number of Citrix Virtual Apps servers in each Zone. |
| SERVERS IN ZONES | |
| Server Name | The name of the Citrix Virtual Apps Server. |
| IP Address | The IP Address of the Citrix Virtual Apps Server. |
| Farm Name | The name of the Farm under which Citrix Virtual Apps Server is Configured. |
| Zone Name | The name of the Zone in which Citrix Virtual Apps Server belongs to. |
| Zone Ranking | The ranking of server(like Most Preferred, Preferred, Default Preference, Not Preferred) in the Zone. |
| Domain Name | The domain name to which Citrix Virtual Apps Server belongs. |
Applications
| Parameter | Description |
|---|---|
| PUBLISHED APPLICATIONS | |
| Application Name | The name of the Published Application. |
| Application ID | The Application ID is a number that uniquely identifies the application even if the application name changed. |
| Server Name | The name of the Citrix Virtual Apps Server in which the application get published / deployed. |
| Farm Name | The name of the Farm in which application get published. |
| Permissions | The value of the application Read Only flag. Values are Read Only, Read/Write |
| Folder Name | The client's Program Neighborhood folder. |
| Application Status | The value of the 'Enable application' flag. When you publish an application, it is enabled by default. Enabled applications are then available to the users specified when the application was published. Disabled applications are not available to users. |
Sessions and Clients
| Parameter | Description |
|---|---|
| SESSION DETAILS | |
| Session ID | The unique ID for each session created in Citrix Virtual Apps Server- |
| Session Name | The name of the Session |
| Session User | The name of the user who is running the Session |
| Session State | The Current state of the Session: userLoggedOn, connectedToClient, connectingToClient, shadowingOtherSession, loggedOnButNoClient, waitingForConnection, listeningForConnection, resetInProgress, downDueToError, initializing. |
| Client Name | The session client name. The session client name is usually the client device name |
| Number of Applications | The number of applications in Session |
| LogOn Time | The session logon time |
| Connect Time | The connect time of the session |
| Current Time | The current time of the session |
| Last Input Time | the session's last input time. |
| Disconnect Time | The last session disconnect time. If the session is connected, the time is 0 for all the values. |
| ICA CLIENT DETAILS | |
| Client Name | The session client name is usually the client device name. |
| Client Address | The network address of the client. |
| ICA Buffer Length | The ICA buffer length of the session. |
Monitoring Xml Service All About Citrix App
Event Log
Monitoring Xml Service All About Citrix Password
Monitoring Xml Service All About Citrix Client
| Parameter | Description |
|---|---|
| Rule Name | The name of the event log rule |
| Log File Type | The Log File Type - Application, system, security, file replication service, DNS Server or directory service. |
| Source | The Application which created the event. |
| Event Id | The Event ID associated with the Event Log File. |
| Type | The Event Type - Error, Warning, Information or Event of Any Type. In case of Security Events, the types would vary between Success Audit and Failure Audit. |
| User Name | The system component or User account that was running the process which caused the event. |
| Description | A description of the event. |
| Generated Time | The time when the event entry was submitted. |