Application UI Unresponsiveness Metrics
Whenever an application’s user interface is unresponsive for more than a few hundred milliseconds uberAgent collects information like the application name (even for App-V, Java and UWP apps), application version and the unresponsiveness duration.
Note: processes are auto-grouped into applications, i.e. the application name is determined automatically without requiring any configuration. Information on how this works are available here.
- Source type:
- Used in dashboards: Application UI Unresponsiveness, Process UI Unresponsiveness, Single Machine Detail, Single Application Detail, Single User Detail
- Enabled through configuration setting:
- Related configuration settings: n/a
- Supported platform: Windows
|Field||Description||Data type||Unit||Measurement type||Example|
|AppId||Associated application ID. Used by uberAgent to lookup application names and populate field
|SessionGUID||Unique identifier that is generated by uberAgent when the session is created.
Valid for this session only.
|HasFocus||Indicates if the application is in foreground (is being used actively). Possible values:
|Field||Description||Data type||Unit||Measurement type||Where available||Example|
|AppName||Associated application name||String||Snapshot||Splunk data model, Splunk SPL||Google Chrome|
|UIDelayS||UI delay/unresponsiveness||Number||s||Sum||Splunk data model||5|
|HasFocusNumber||Indicates if the application is in foreground (is being used actively). Possible values:
||Number||Snapshot||Splunk data model||1|
|ProcName||Process name||String||Snapshot||Splunk data model||chrome.exe|