Exclude Outliers from Latency Last and Logon Duration Aggregated Average Calculations
  • Dark
    Light
  • PDF

Exclude Outliers from Latency Last and Logon Duration Aggregated Average Calculations

  • Dark
    Light
  • PDF

Introduction

In some cases, values shown for the Logon Duration and Latency Last metrics are distant from observed values of other sessions. This could skew the results of aggregated values for both, the Sessions Avg. Protocol Latency and the Avg. Logon Duration metrics. For more information on these 2 session metrics, refer to the Sessions View & Actions article.

With ControlUp version 8.6 you can exclude extreme values from being considered in aggregated average calculations. In this article, we will show you how to set an upper limit for values of the Logon Duration and Latency Last metrics.

Prerequisites

Before you can start using this feature, make sure you meet these requirements:

  • ControlUp Version 8.6
  • Administrative access to the ControlUp Monitor machine. This is needed to run the new Powershell cmdlet.

What are aggregated metrics?

Before you define upper limits, you need to understand what aggregrated metrics are. Aggregated values are average values calculated by ControlUp. For example, the Avg. Logon Duration metrics is the mean of all Logon Duration values for all sessions in a specific folder. You can find aggegrated columns in the Folder tab in the ControlUp Real-Time Console.
image.png

In Solve, they are shown as widgets under the User Sessions tab in the Discovery menu.
image.png

Aggregated metrics that are session-related and relevant for this article are Sessions Avg. Protocol Latency and Avg. Logon Duration.

When and why should I set limits?

The question is: Why should you change the limits? An example that illustrates the problem with outliers is shown below:

image.png

This screenshot shows the Avg. Protocol Latency widget in Solve. In the line graph, you can see that the average values range between 800 ms and 2400 ms although most values in the Latency Last columns are below 500 ms. The 3 abnormal data values in the Latency Last column make the information in the widget less useful for the user.

How can I change limits?

You can set upper limits for the Logon Duration and Latency Last by using a new PowerShell cmdlet Set-ColumnLimitConfig.

To set the upper limit:

  1. Connect to your monitor machine with a user that has administrative rights.
  2. Open a PowerShell IDE. Make sure you start it as an administrator.
  3. Navigate to the Monitor folder C:\Program Files\Smart-X\ControlUpMonitor\Version 8.6.x.x and execute the following command:
Import-Module -name .\ControlUp.PowerShell.User.dll

image.png
4. Set the upper limit according to your preferred value by executing the following PowerShell command:

Set-ColumnLimitConfig -TableName "Sessions" -ColumnName "LogonDuration" -Limit 99

As a result, values in the Logon Duration column above 99 seconds are not taken into account when calculating the Avg. Logon Duration.

The Latency Last column also allows you to set an upper limit. To exclude values above 100 ms from the calculation of the Sessions Avg Protocol Latency, run the following PowerShell command:

Set-ColumnLimitConfig -TableName "Sessions" -ColumnName "SessionLatency" -Limit 100
Note

As shown above, the PowerShell cmdlet does not require a unit as an input parameter. It is not necessary to provide seconds, milliseconds, etc. to the script.

How can I retrieve current limits?

While the Set-ColumnLimitConfig command is used for setting a limit, you can use the Get-ColumnLimitConfig with the same input parameters to retrieve the currently set limit. The following command returns the currently used upper limit for the Logon Duration column:

Get-ColumnLimitConfig -TableName "Sessions" -ColumnName "LogonDuration"

image.png

Color scheme for exceeding upper limits

Whenever the Logon Duration or Latency Last metrics exceed the configured upper limit, the color scheme of this value changes accordingly, regardless of how the thresholds are configured in the Stress Level Settings.

A value greater than 35 is highlighted in red when the configured upper limit for the Logon Duration is 35, as shown in this example:
image.png


Was this article helpful?