Login VSI releases new Product update of Login PI

About Login PI:

Login PI is the newest product from Login VSI. While the product Login VSI is used for load testing, benchmarking and for planning activities, PI continuously monitors the environment and test the performance of your virtual desktop environment.

User Experience Monitoring:

Login PI works with so-called launcher machines which simulates user sessions to virtual Desktop environments like:

  • Citrix XenDesktop/XenApp
  • VMware Horizon View
  • VMware Horizon DaaS
  • Remote Desktop Host Session servers

See the screenshot below for the different connectors which are by default included.

PI Connectors

Workloads:  

At configured intervals, PI launches a client connection, just as a regular user would do and measures the Logon time, running time and application start times. All the information is stored in a SQL database.  The workload of this simulated user is very similar compared with the VSI product. It simulates real user activity such as opening a website, starting Office applications and Adobe.

Within the product there are some default workloads based on:

  • Native Windows Apps
  • Office Applications (multiple Languages)
    • 2003
    • 2007
    • 2010
    • 2013
    • 2016

When you have specific application monitoring needs, custom workloads can be created to measure the desired application responsiveness from applications such as SAP, or any others.

workload settings

Running Login PI session from a PI launcher machine.

running session

Alerts:

With the Alert settings we could specify the threshold value of a certain action. If the action result is higher than the threshold, an alert is generated. This is shown in the PI console, but is also written to Applications and Services LogsPI Alerts within the Event Viewer.

Alerts could be set as auto configured or can be set manually by typing the desired threshold.

thresholds

Charts:

With the historical information we could create charts and recognize over time, if there are specific trends visible in the performance of the environment, if a certain change influences the performance or if there were any interrupts or delays.

Charts

 

So what’s new:

This product update release of Login PI is all about stability. See below for the complete release notes:

New Features:

  • The format in the eventdata of the Login PI events have changed, so monitoring solutions can parse it better
  • Some of the titles and descriptions in interface have changed to be more intuitive
  • The interface now provides feedback when the launcher authentication is denied so it is easier to know when to resolve this
  • Configured connection settings for the desktop broker are now displayed in the launcher console window for easier troubleshooting
  • The launcher IDs are programmed to stay the same when upgraded to a newer version
  • The server settings of the PI server will stay the same when upgraded to a newer version

Resolved Bugs:

  • Exception errors on ASP.NET
  • The BBC website is now loaded before reporting results to Login PI
  • Leap year day, Feb 29, was not working in the charting module
  • Fixed values could not be set for thresholds

 

During the installation of the new Login PI product I noticed one big thing that isn’t part of the release notes.

Before, the PI agent used the PI share for getting the workload settings. Seems this is removed in the new version and now the agent downloads, though the use of the login script, the content though the PI API. Meaning that for every session that is launched the content is downloaded to make sure we have the correct and up-to-date files needed for the measurement.

Below a part from the logon script, that removes the old and downloads the new content form the PI server.

<em>:: Remove old %PI_RUNTIME_FOLDER% folder (if exists)

IF EXIST "%PI_RUNTIME_FOLDER%" rmdir /s /q "%PI_RUNTIME_FOLDER%"MD %PI_RUNTIME_FOLDER%

MD %PI_RUNTIME_FOLDER%

%SystemRoot%system32WindowsPowerShellv1.0powershell.exe -ExecutionPolicy ByPass -Command "try{; &amp; { (New-Object Net.WebClient).DownloadFile('%API_URL%', '%CMD_LOCATION%'); Start-Process -FilePath '%CMD_LOCATION%'}} Catch {  $ErrorMessage = $_.Exception.Message; $sec = 30; Do { $sec-- ; Clear-Host; Write-Host -foregroundcolor red 'Something went wrong: '$ErrorMessage; Write-Host 'Waiting for'$sec' seconds until starting the logoff command'; start-sleep -seconds 1} while($sec -ne 1); Start-Process -File 'shutdown.exe' -ArgumentList '-l -f' }"</em>

Why is this important?

If we are looking at a PI implementation with launchers in different locations, environments or a multi-tenant setup. We could install a single PI server and create a separate launcher for every location. We don’t have to think about making the share available across these different launcher locations or have it replicated.

The only thing we need, is having the logon script available for the PI user in every environment we have to monitor and have a route to the PI server.  The last step we have to do is to change the Firewall to allow the following rules:

Source: [Target environment] |  Destination [PI server] | Service port 8080, 9090, 9091

Source: [PI launcher] |  Destination [Target environment] | Service [port used by the protocol of choice]

 

More information about Login PI can be found on: https://www.loginvsi.com/products/login-pi

This post Login VSI releases new Product update of Login PI appeared first on vClouds.


This post was originally published on this site
Comments are closed.