Skip to main content
ComponentsEngineJS ProfilerMobile AppRPA Bot RecorderRUM WindowsAgent
Availability2026.2

KPI Categories

Groups of Windows KPIs

User Interaction KPIs

Works regardless of language

Error and Diagnostic KPIs

Crashes and diagnostic signals

From Detection to Resolution

Combine KPIs to resolve issues

​
Overview

GermainUX provides real-time KPIs that reveal how users experience and interact with Windows applications. These KPIs help teams:
  • Identify slow, failed, or unsuccessful user interactions
  • Detect application freezes, crashes, and errors
  • Understand application usage and adoption
  • Analyze searches, navigation, and workflows
  • Investigate unexpected UI behavior
  • Replay the sequence of events leading to an issue
  • Measure the frequency, duration, and business impact of problems
  • Trigger alerts or automated actions when defined conditions occur
The user-experience and application-level KPIs are technology-agnostic. They can monitor applications built with .NET, C#, C++, Win32, WPF, Windows Forms, Delphi, Qt, Java, Electron, and other Windows technologies.

​
KPI Categories

​
User Experience KPIs

These KPIs can be filtered, segmented, correlated, and analyzed by dimensions such as:
  • Application
  • Application version
  • User
  • Device
  • Location
  • Environment
  • Window or view
  • UI control
  • Business action
  • Time period

​
User Interaction KPIs

Windows interaction monitoring operates at the application and UI level, independently of the programming language used to build the application.

​
Windows User Click

A Windows User Click represents a business-relevant interaction matching a configured selector. Examples include:
  • Opening a customer record
  • Approving an order
  • Saving a transaction
  • Moving to the next workflow step
  • Selecting an account or product
  • Double-clicking a data-grid row
Unlike raw mouse telemetry, this KPI identifies actions that have specific business meaning. GermainUX can measure the response time following each matched interaction and correlate it with related application events.

​
Windows Mouse Click

A Windows Mouse Click records every detected mouse click on a UI control. Use this KPI to:
  • Analyze general interaction patterns
  • Identify frequently or rarely used controls
  • Generate click heatmaps
  • Investigate repeated or unexpected clicking
  • Compare raw activity with configured business actions
A Windows Mouse Click is unconditional telemetry. A Windows User Click is generated only when an interaction matches a configured business-action selector.

​
Windows Keyboard

A Windows Keyboard KPI records configured command-style keyboard interactions, including:
  • Enter
  • Escape
  • Function keys
  • Ctrl combinations
  • Alt combinations
  • Windows-key combinations
It is intended to capture commands and shortcuts, not ordinary text entered into fields. A Windows Search KPI captures:
  • The search term entered by the user
  • The application and view in which the search occurred
  • Related events and subsequent user actions
This KPI helps identify:
  • Common search terms
  • Searches that produce no useful result
  • Repeated searches
  • Search-related abandonment
  • Ineffective navigation or product discovery
  • Differences in search behavior across user groups

​
Windows Change Event

A Windows Change Event reports modifications to input controls, including:
  • Text-field edits
  • Checkbox selections
  • Radio-button selections
  • Dropdown changes
  • Other supported value changes
These events help reconstruct user workflows and explain how application state changed before an error, failure, or unexpected outcome.

​
Application Performance and Reliability KPIs

​
Windows Freeze

A Windows Freeze occurs when a monitored application window stops responding to Windows messages. GermainUX periodically checks the responsiveness of monitored windows. When a frozen window recovers, GermainUX records:
  • The duration of the freeze
  • The user session
  • Related user interactions
  • Application events occurring around the same time
  • The associated session replay, when enabled
The event is recorded when the window recovers because the total freeze duration is not known until that point. This KPI helps identify:
  • Temporarily unresponsive interfaces
  • Long-running operations on the UI thread
  • Application stalls
  • Resource contention
  • External calls blocking user interaction
  • Repeated freezes affecting the same users, devices, or workflows

​
Windows Crash

A Windows Crash is generated when a monitored process terminates with a nonzero exit code. This can include failures caused by:
  • Unhandled exceptions
  • Access violations
  • Windows Error Reporting failures
  • Fast-fail termination
  • Other abnormal process exits
The crash can be correlated with the preceding user actions, application events, errors, resource conditions, and session replay.

​
Windows App Event

A Windows App Event represents an application or window lifecycle change reported by the Windows UI worker. Events include:
  • Application startup
  • Application shutdown
  • Window creation
  • Window destruction
These events help teams understand:
  • Application launch frequency
  • Startup and shutdown behavior
  • User navigation between windows
  • Unexpected window creation
  • Application lifecycle immediately before a freeze, crash, or error

​
Error and Diagnostic KPIs

​
Windows User Error

Despite its KPI name, Windows User Error identifies an error presented to the user; it does not necessarily mean that the user caused the error. The KPI is generated when the title of a newly created window matches a configured pattern, such as:
  • Error
  • Failed
  • Failure
  • Exception
  • Unable to complete
Use this KPI to identify and analyze visible application failures without configuring every individual control inside each error dialog. Where helpful in documentation and dashboards, this KPI can be described as a Windows User-Facing Error to distinguish it from user validation feedback or an incorrect user action.

​
Windows System Error

A Windows System Error reports error-level events occurring on the monitored Windows system. These events provide technical evidence that can be correlated with:
  • Application crashes
  • Freezes
  • Slow interactions
  • Failed workflows
  • User-facing errors
  • Device-specific problems

​
Windows System Warning

A Windows System Warning reports warning-level Windows events. Warnings may indicate emerging conditions that have not yet caused a complete failure but could explain degraded performance, instability, or intermittent user issues.

​
Windows User Session Replay

Windows User Session Replay provides the evidence needed to understand what occurred before, during, and after an application problem. It can help investigate: Session replay can be opened from an affected KPI instance, allowing analysts to move from an aggregate issue directly to the specific session in which it occurred. Because replay is captured at the Windows application level, it is not limited to a specific programming language or framework.

​
UX-Level and Technology-Level Analysis

Many Windows KPIs are useful for both user-experience and technical analysis.

​
UX-Level Analysis

UX-level analysis focuses on the effect experienced by users:
  • What action did the user perform?
  • How long did the application take to respond?
  • Did the expected result appear?
  • Did the user encounter an error, freeze, or crash?
  • Which users and workflows were affected?
  • How much productivity was lost?
  • What did the user do next?

​
Technology-Level Analysis

Technology-level analysis focuses on the underlying application behavior:
  • Which process, window, or component was involved?
  • Did the application terminate abnormally?
  • Was the UI thread unresponsive?
  • Which system errors or warnings occurred?
  • Did resource usage increase?
  • Did a .NET exception, garbage-collection pause, or slow HTTP call correlate with the issue?
  • Is the problem limited to a particular application version, device, or environment?
Combining both levels helps teams move from an observed user issue to its technical cause.

​
Technology-Agnostic Windows Monitoring

GermainUX monitors the application and user experience rather than depending exclusively on the underlying development language. The Windows UX, interaction, reliability, error, and replay KPIs can therefore apply to applications built with: The exact richness of control-level monitoring can vary based on how much information the application exposes through Windows UI Automation.

​
.NET-Specific KPIs

Runtime-specific metrics are available for eligible .NET applications when the GermainUX CLR Profiler is attached. These can include:
  • .NET exceptions and stack traces
  • Garbage-collection pauses
  • Generation 0, 1, and 2 collection counts
  • CLR CPU stack sampling
  • .NET thread-pool metrics
  • http://ASP.NET request queues
  • IIS metrics
For these metrics, see .NET Application Monitoring KPIs.

​
From Detection to Resolution

Windows KPIs can be used together to investigate and resolve an issue:

​
Get Help

Contact GermainUX Support

The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

Can't find what you need?

Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.