Measuring Total Login Time

Overview

To achieve peak performance for your application and virtual desktop environments, it’s crucial to measure total login time. Login Enterprise assesses not only the application functionality but also the efficiency of user interactions, including the login process. The login time, measuring the duration it takes for a user to access an application or virtual desktop, is a significant performance metric influencing user satisfaction and overall system efficiency.

Why measure login time?

  • Improved User Experience: Swift login times play a vital role in creating a positive user experience. In the competitive world of applications and virtual environments, a rapid and responsive login process forms the foundation for engaging user interactions.
  • Performance Optimization: Measuring login time provides valuable insights into system efficiency. Identifying bottlenecks or delays enables you to make informed decisions for optimizing performance, ultimately speeding up users' access to their resources.
  • Scalability Planning: Understanding login times is critical for scalability planning. As your user base expands, it becomes essential to maintain efficient login processes. Accurate measurement helps anticipate and address potential challenges that may arise due to rising demand.
  • Availability Assurance: The login process typically marks users' first interaction with your system. Monitoring and optimizing login times contribute to overall system availability, mitigating the risk of user frustration due to delays or interruptions.

How it works with Login Enterprise

When a session initiates, the Engine looks for a process named 'explorer.exe'. The Engine captures the start time of this process and communicates this data to the appliance. This observation forms the foundation for the appliance to determine the total login time—the duration spanning from the moment a session is started by the launcher until the initiation of the 'explorer.exe' process. The total login time metric is then available from one of the charts in the test results.

Currently, the behavior for deciding what process to use to measure total login time is as follows:

  • Citrix Storefront and NetScaler Connector (published desktop/app) = wfshell or picashell
  • All other connector types = explorer

Considerations for Published Apps

In scenarios involving published apps, the presence of 'explorer.exe' in the Engine's session may not apply, as these apps operate differently. The appliance may face challenges locating 'explorer.exe' during the login process for published apps, potentially impacting the accuracy of total login time measurements.

Custom process of measuring total login time

To address the challenges posed by published apps, Login Enterprise allows you to overwrite the default process with a process of your choice. This flexibility ensures that, regardless of the intricacies of your environment, you can tailor the login time measurement to align precisely with your specific configurations and requirements.

Starting from Login Enterprise 5.7, you can customize the process of measuring total login time in one of the following ways:

The process of measuring total login time is backward compatible. That is, if you already changed the process through the internal API, you don’t have to change the setting again.

Regardless of whether the property was named 'shell-executable' or 'shellExecutable' during the new process setup, both names will be displayed in the new field after the upgrade to 5.7.

Custom process of measuring total login time in Login Enterprise UI

The following steps are only relevant if you’ve created your test. If you haven’t already, please do so, and then proceed to customize the process of measuring total login time as outlined below.

  1. Log in to the Login Enterprise with your credentials.
  2. In the Sidebar menu, navigate to Configuration > Manage tests, and select the desired test, e.g. Continuous test.

    68096446-05ab-4449-95d3-bdd2a73dcc30.png

  3. Click on the particular test, scroll down, and find the Test settings.

    d1fe59ca-9606-49be-994e-58c5500cd5c3.png

  4. In the Logon time tracking process, select 'Custom'. (Note that the 'Default' radio button is selected by default).
  5. In the popup window, enter the value for the new process, and save the changes. The value must be without extension. That is, for explorer.exe, the value is 'explorer'.

The default values for Citrix StoreFront and NetScaler Connector are 'wfshell' or 'picashell.' For other connector types, the default value is 'explorer'. You can customize it based on your platform, such as 'wfshell' for Citrix, 'vmware-view-usbd' for VMware, or 'rdpshell' for Microsoft RDP.


ebe732f3-84f4-4762-8b09-21c4af6d0b15.png

Cancelling the popup selects the 'Default' radio button again. Saving the popup value chooses the custom value, updating the field. If you'd like to make further changes, initiate the popup once more.

0aa02f1a-faca-4196-97c4-0850560ec71b.png


The process of customizing the measurement of total login time is the same for all types of tests, including Load tests and Application tests.

Custom process of measuring total login time in Login Enterprise Public API

Accessing the Public API in the Login Enterprise

To access the Public API in the Login Enterprise, follow these steps:

  1. Log in to the Login Enterprise with your credentials
  2. In the Sidebar menu, scroll down and find External notifications.

    Frame 5 (1).png

  3. In External notifications > tab bar menu, select Public API.

    6c126098-a139-4e9f-94a2-c1e51310704c.png

  4. In Public API, click Public API documentation (this will redirect you to the API Reference).

    e293c123-bcb4-4ca1-a075-d61969e12094.png

  5. Under Download OpenAPI specification > v7.0 preview, click API Console Swagger (the Swagger API interface with the v7-preview Public API will open).

    25a39c5a-3ea8-4dde-9013-c020510bff04.png

Creating a GET request in the Public API

To ensure your test is configured correctly, you might want to start with creating a GET request. To do this:

  1. In the OpenAPI Specification, scroll down and find Test.
  2. In Test, click GET /v7-preview/tests/{testId}.

    41a8b8a7-bd9a-4096-b1a1-65947959a36e.png

  3. In the top-right corner, click Try it out.
  4. In testId, paste the ID of your test, and then Execute.

    e6938dbb-85b1-4d45-9f28-0638cf83efb4.png

Looking for the Id in the URL

In the Login Enterprise > Configuration > Manage tests > (e.g. Continuous test) address bar, you will see the URL. Locate a part of the URL that contains the test Id. It often appears as a series of letters, numbers, or a combination of both. Highlight the entire Id in the URL, right-click, and select 'Copy'.


If the server responds with a 200 status code, indicating that the GET request was successful, it will return the requested information in JSON format in the response body. Copy the JSON text from the response body as you will need it when creating a PUT request.

9c4cf24d-e6a6-48e9-a087-40e73faecb25.png

Creating a PUT request in the Public API

To customize the process of measuring total login time in the Public API, you need to create a PUT request. For this:

  1. In the OpenAPI Specification > Test, click PUT /v7-preview/tests/{testId}.

    5e494ea7-db56-4292-80e7-7e681d57abb5.png

  2. In the top-right corner, click Try it out (The Request body field will open).
  3. In testId, paste the ID of your test.
  4. In the Request body, paste the JSON text you copied from the response body in the GET request.
    In the "logonTimeTrackingProcess" property, specify the value for the new process. For example, if it’s explorer.exe, enter "explorer".

    In the "logonTimeTrackingProcess" property, specify the value for the new process. For example, if it’s explorer.exe, enter "explorer".

  5. Click Execute.

914348a3-1b91-4fae-999e-7928b5a37132.png

If the server responds with a 200 status code, indicating that the PUT request was successful, it will return the requested information in the response headers.

01e7ba93-f630-43a6-97dc-7b81dd03e7e9.png

When you select the ' Custom ' radio button, the new process field will appear in the Test settings.


Overall, the Login Enterprise login time measurement feature provides a nuanced understanding of user experience, allowing you to make informed decisions for optimizing performance and enhancing the efficiency of your applications and virtual desktop environments.

Additional resources