These KPIs provide visibility into what users experience while interacting with the Windows application, including application startup and shutdown, user interactions, searches, UI changes, freezes, crashes, errors, and complete session replay.
Windows applications built with technologies such as .NET, C++, Win32, WPF, Windows Forms, Delphi, Qt, Java, Electron, and other Windows application frameworks can be monitored using the same user experience and application-level KPIs.
📊 User Experience KPIs
|
KPI Name |
UX Level |
Technology Level |
Description |
|---|---|---|---|
|
Windows User Session Replay |
X |
X |
A millisecond, pixel-perfect playback of an end-user's session and what that user "saw" and "did" on his/her screen including: interactions, clicks, navigation, and UI changes. |
|
Windows User Login |
X |
X |
Count of Windows user logins. |
|
Windows User Click |
X |
X |
A business-meaningful click matching a configured selector (vs. Mouse Click's unconditional telemetry), measured by response duration. |
|
Windows Mouse Click |
X |
X |
Raw, unconditional telemetry for any mouse click on a UI control. |
|
Windows Keyboard |
X |
X |
A key press matching a configured command-key pattern (Enter, Escape, Ctrl/Alt combos, function keys). |
|
Windows Search |
X |
X |
A click on a configured search-trigger control, captured together with the search term it enters. |
|
Windows Change Event |
X |
X |
A change to an input control's value (text field edit, checkbox/dropdown toggle). |
⚙️ Application Performance & Reliability KPIs
|
KPI Name |
UX Level |
Technology Level |
Description |
|---|---|---|---|
|
Windows Freeze |
X |
X |
Duration a monitored window was unresponsive before recovering (SendMessageTimeout polling); recorded on recovery, not onset. |
|
Windows Crash |
X |
X |
The monitored process exited with a non-zero code (unhandled exception, access violation, WER fast-fail); any non-clean exit qualifies. |
|
Windows App Event |
|
X |
Application lifecycle events (Startup, Shutdown, window Created/Destroyed) reported by the UIA worker. |
🤝 User Interaction KPIs
Windows Application Monitoring captures user interactions independently of the programming language or application framework used to build the application.
|
KPI Name |
UX Level |
Technology Level |
Description |
|---|---|---|---|
|
Windows User Click |
X |
X |
A business-meaningful click matching a configured selector (vs. Mouse Click's unconditional telemetry), measured by response duration. |
|
Windows Mouse Click |
X |
X |
Raw, unconditional telemetry for any mouse click on a UI control. |
|
Windows Keyboard |
X |
X |
A key press matching a configured command-key pattern (Enter, Escape, Ctrl/Alt combos, function keys). |
|
Windows Search |
X |
X |
A click on a configured search-trigger control, captured together with the search term it enters. |
|
Windows Change Event |
X |
X |
A change to an input control's value (text field edit, checkbox/dropdown toggle). |
Error & Diagnostic KPIs
|
KPI Name |
UX Level |
Technology Level |
Description |
|---|---|---|---|
|
Windows User Error |
X |
X |
A new window whose title matches a configured "user-facing error" pattern. |
|
Windows System Error |
|
X |
Error events on the monitored system. |
|
Windows System Warning |
|
X |
Warning events on the monitored system. |
🎥 Session Replay
|
KPI Name |
UX Level |
Technology Level |
Description |
|---|---|---|---|
|
Windows User Session Replay |
X |
X |
A millisecond, pixel-perfect playback of an end-user's session and what that user "saw" and "did" on his/her screen including: interactions, clicks, navigation, and UI changes. |
Windows User Session Replay provides a visual record of the user's experience and can be used to investigate issues such as:
|
Issue |
Details |
|---|---|
|
Application freezes |
|
|
Crashes |
|
|
User-facing errors |
|
|
Unexpected UI behavior |
|
|
Slow or unsuccessful interactions |
|
|
Navigation issues |
|
|
Workflow problems |
|
|
Changes to input controls |
|
|
User actions leading up to an application problem |
|
Because the session is captured at the Windows application level, it is not tied to a specific development language.
🌐 Technology-Agnostic Windows Monitoring
Windows Application Monitoring focuses on the application and user experience rather than the underlying programming language.
The same monitoring capabilities can therefore be applied to applications built with:
|
Technology |
Notes |
|---|---|
|
.NET |
|
|
C# |
|
|
C++ |
|
|
Win32 |
|
|
WPF |
|
|
Windows Forms |
|
|
Delphi |
|
|
Qt |
|
|
Java |
|
|
Electron |
|
|
Other Windows application technologies |
|
Language- or runtime-specific metrics, such as CLR garbage collection, .NET exceptions, http://ASP.NET request queues, IIS metrics, or .NET thread-pool metrics, are documented separately under .NET Application Monitoring KPIs.