This discussion addressed whether ControlUP keeps a log of user input delay. It was suggested to use the Monitor PS cmdlets Export-CUQuery to query the Sessions table and Field UserInputDelay. An example was given on how to refresh this table every two seconds for a duration of 200 seconds using Invoke-CUQuery and Export-Csv.
Read the entire ‘Logging User Input Delay with ControlUP’ thread below:
Does ControlUP keep a log of user input delay anywhere, or is it merely a realtime thing?
My suggestion: Use the Monitor PS cmdlets (in this case Export-CUQuery) and write a script that manually queries the Sessions table, Field UserInputDelay. As this is a real-time metric, I think you would need to query this table quite frequently to get useful results
An example with the Invoke-CUQuery (which you could basically use as well to send the output to a file (Out-File))
If you want to refresh every 2 secs (for a duration of 200 seconds)
for ($i = 0; $i -lt 100; $i++) {
`$now = Get-Date`
`$queryResult = (Invoke-CUQuery -scheme Main -Table Sessions -Fields UserInputDelay, ADDN, sServerName -Where "UserInputDelay > 0.0").Data`
`$output = $queryResult | Select-Object *,@{Name=’Timestamp’;Expression={$now}}`
`$output | Export-Csv -Path ‘C:\tmp\UserInputDelayOverview.csv’ -Append -NoTypeInformation`
`Start-Sleep -Milliseconds 2000`
}
Continue reading and comment on the thread ‘Does ControlUp keep a log of user input delay anywhere, or is it merely a realtime thing?’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers