Skip to main content

uberAgent 3.5 is all about Application Reliability

  • by Helge Klein
  • February 11, 2016

The new uberAgent 3.5 brings some fascinating new capabilities for analyzing application UI performance. These go along with even further reduced resource footprint and many dashboard improvements.

Application UI Unresponsiveness

Everybody has seen windows with the text not responding added to their titles. The operating system marks windows in such a way to notify the user that the application has not updated the UI for the past five seconds. Whenever that happens, the user’s workflow is interrupted, time is lost.

That is exactly what application UI unresponsiveness is about. uberAgent tracks when application UIs are not responding to user input even for very short periods of time (a few hundred milliseconds) and makes the resulting data readily available per user, application, machine, or as a total:

uberAgent for Splunk - wait times for unresponsive applications

uberAgent now also constantly determines which application is in the foreground. With that we can determine which of the many running applications is used to what extent. This adds nicely to uberAgent’s existing application inventory and application usage capabilities.

Advanced Filtering on any Dashboard

We have significantly improved dashboard filtering capabilities. You can now combine multiple filters, and you can filter by Active Directory domain, OU, and site, by Citrix Farm, delivery group and machine catalog, by hardware model and manufacturer, by OS build number, type and version. This advanced filtering functionality is available on every dashboard.

uberAgent for Splunk - multiple dashboard filters

And More

There is a lot more new and improved stuff than we could describe here. Go try it for yourself: setting up uberAgent is super-fast and easy.

As always upgrading is highly recommended. Please see the changelog for details. The new version can be downloaded here.

About uberAgent

uberAgent is a Splunk agent for Windows end-user computing, focused on user experience and application performance monitoring. Its highlights include detailed information about boot and logon duration (showing why and when boots/logons are slow), network latency per target and process, process startup duration, application usage metering, browser performance per website and remoting protocol insights.

About vast limits GmbH

vast limits GmbH develops enterprise-grade tools for administrators. These include uberAgent for Splunk (user experience and application performance monitoring), Delprof2 (profile deletion), SetACL and SetACL Studio (permissions management). Our tools have been downloaded more than half a million times and are used by enterprises worldwide.

Our founder, Helge Klein, is an experienced consultant and developer. As a consultant, he has worked in Windows and Citrix projects for large corporations. As a developer, he architected the user profile management product whose successor is now available as Citrix Profile Management. In 2009 Helge received the Citrix Technology Professional (CTP) award, in 2011 he was nominated a Microsoft Most Valuable Professional (MVP), in 2014 he was a Splunk Revolution Award Winner, in 2015 he became a VMware vExpert. Helge can be found on Twitter as @HelgeKlein. He frequently presents at conferences and user group events like Citrix Synergy, Splunk .conf, BriForum or E2EVC.


Your email address will not be published. Required fields are marked *


Hello, Thank you for this post.

I would like to know :
- What is the values range for a good/normal UI latency, or in other words which values should not be exeeded.
- What is the difference between Application UI latency per process Application UI latency per aplication, because in my tough it should be quite the same but I noticed that
the ranking is not the same.
Is there any website or document that explains how to read those graphs and interpret them and gives more detailed information ?

Thank you in advance,