LoginPI 3 - Latency
LoginPI3 - Latency
The new update of LoginPI3 (3.2.8) will bring back an old feature of LoginPI2: Latency.
Latency will be measured for the three vendors: Microsoft RDP, VMware and Citrix.
LoginPI3 measures latency the same way it did in LoginPI2, by reading performance(WMI) counters that each of the protocols provides. These counters are the same as the counters shown in Performance Monitor.
These counters are present on the target environment(Session), the engine will read these settings and store them in the backend. Through API calls this information is presented on the Dashboard and Charting. These counters are measured every minute, and are shown as raw data in charting and dashboard.
Let's get started!
With the new update LoginVSI brought sorting of applications, this is a welcome change considering it was random before.
When we create an environment we are presented with the schedule. From there we can add applications to it and drag and drop them in the order we want.
Within the environment settings we can set the actual threshold for latency. This threshold is used for emailing and also on the dashboard, when a measurement goes over the value it is shown nicely in the environment dashboard.
For the emailing part we have to enable the Global Email Settings, when this is not configured the email settings will not appear. In these settings we can specify when we want to receive an email as shown in the picture below.
When you have configured the email settings the following email will be sent once the measurements have exceeded the threshold for x amount of times within x amount of minutes.
Now we will take a look at the dashboard changes that the new version brought with it.
Update 3.2 will have some new additions to the dashboard. In the following image you can see that they added a new bar for Latency that reached the threshold limit.
If you go deeper into a specific environment we see that a new dial has been added specifically for Latency.
In the top left screen you can see the amount of sessions that are active and how many launchers.
The latency dial is clickable and will provide us with further information, such as which launcher has reported latency and what the latest, maximum, minimum and average latency is specifically for that launcher.
In the hourly chart you can see all the raw latency data that comes in. When hovering over the bubbles you can see some extensive information on what time the measurement came in, what the value was, which protocol is measured and on which host/launcher this measurement was taken. Furthermore, you can also see which user was logged in during that time, this can come in handy when we want to see some logging for that specific timeframe.
In the daily chart you can see a nice overview on what the latency measurements were during the day. When you hover over the line you can see additional information for that specific time slot. As you can see in the picture we had a nice stable environment.
In the SLA report tab an option for an SLA agreement has been added: Latency.
By enabling this threshold, the generated report will be extended to show latency.
We can set the schedule to daily or monthly, for Lab purposes I have set the schedule to daily.
That's all there is to the new latency feature for now. If you want to know all the new features or bug fixes/improvements please refer to the official release notes of LoginPI3.
Link: LoginPI3 Release Notes
If you are using Windows 7 in your environment and can't get Latency to work with the RDP protocol, check out my other blog that covers enabling latency on Windows 7.
Thanks for reading!