> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# KPIs for .NET Monitoring, Automation & Session Replay

> GermainUX provides KPIs for monitoring user experience, application performance, code execution, errors, processes, and availability of .NET applications.

Components
[`Agent`](https://docs.germainux.com/main/germainux-agent)
[`Engine`](https://docs.germainux.com/main/germain-ux-engine)
[`JS Profiler`](https://docs.germainux.com/main/germain-ux-js-profiler)
[`Mobile App`](https://docs.germainux.com/main/germain-ux-mobile-app)
[`RPA Bot Recorder`](https://docs.germainux.com/main/germain-ux-rpa-bot-recorder)
[`RUM Windows`](https://docs.germainux.com/main/germainux-rum-windows)

Availability
2026.2 or later

> [card] [Browser User-Experience KPIs](#browser-user-experience-kpis)
>
> Segment by page and device

> [card] [Business-Process KPIs](#business-process-kpis)
>
> Measure processes across channels

> [card] [Synthetic-Monitoring KPIs](#synthetic-monitoring-kpis)
>
> Bots validating key applications

> [card] [Alerts and Reports](#alerts-and-reports)
>
> Alerts for key conditions

## KPIs for .NET Monitoring, Automation, and Session Replay

## Overview

GermainUX provides KPIs for monitoring the user experience, application performance, code execution, errors, business processes, infrastructure, and availability of .NET applications.

Monitoring can cover:

* ASP.NET and ASP.NET Core web applications
* .NET APIs and services
* Native Windows applications built with .NET
* Background services and scheduled processes
* Application integrations
* Hosts, processes, databases, and containers
* Synthetic user scenarios

The available KPIs depend on the application type and deployed GermainUX components.

## Browser User-Experience KPIs

For browser-based .NET applications, GermainUX RUM JS can collect:

| KPI | Description |
| - | - |
| User Session | Captures session duration, activity, and application context |
| User Session Replay | Reconstructs captured user activity |
| Page View | Records pages, routes, and application views |
| User Click | Captures interactions with links, buttons, and controls |
| User Action | Measures configured interactions and their duration |
| Browser Event | Captures browser events affecting the user experience |
| JavaScript Console Event | Records JavaScript errors and configured console messages |
| Outbound HTTP Request | Measures browser requests, duration, and status |
| Resource Load | Measures scripts, stylesheets, images, and other resources |
| User Feedback | Captures ratings, comments, and related session context |

These KPIs can be segmented by application, environment, page, user, browser, device, location, release, or business process.

## Native Windows Application KPIs

GermainUX RUM for Windows monitors the experience of users working in supported native Windows applications developed with technologies such as C# and .NET.

Available telemetry can include:

* Application start and exit
* Window and view activity
* User clicks
* Keyboard activity
* Control and value changes
* Navigation

> [accordion] Show all 14
>
> * Searches
> * Application freezes
> * Application crashes
> * User-session duration
> * User inactivity
> * Errors visible to the user
> * Lost productivity
> * Session Replay

Session Replay reconstructs captured application activity and helps teams understand what occurred before a crash, freeze, error, or inefficient workflow.

The available details depend on the application framework, controls, monitoring configuration, and privacy settings.

## .NET Code and Transaction KPIs

The GermainUX Code Profiler can monitor supported .NET application code and transactions.

Common measurements include:

| Measurement | Description |
| - | - |
| Transaction duration | End-to-end time of a monitored transaction |
| Method duration | Time spent executing a method |
| Cumulative time | Total time associated with a method and its downstream calls |
| Exclusive time | Time spent only in the selected method |
| Invocation count | Number of times a method or transaction executes |
| Exception count | Number of captured exceptions |
| Error rate | Percentage of monitored executions that fail |
| Database duration | Time associated with monitored database operations |
| External-call duration | Time spent waiting for downstream services |
| Throughput | Number of transactions processed over time |

Code-level visibility depends on the supported .NET runtime, profiler configuration, deployment permissions, and selected monitoring scope.

## Error and Reliability KPIs

GermainUX can monitor errors visible through deployed components and configured data sources, including:

* .NET exceptions
* Unhandled exceptions
* Application crashes
* Application freezes
* HTTP errors
* API failures

> [accordion] Show all 14
>
> * JavaScript errors
> * Browser resource failures
> * Network timeouts
> * Database errors
> * Log-file errors
> * Failed business-process steps
> * Synthetic transaction failures
> * Errors displayed to users

Errors can be categorized by application, environment, transaction, exception, message, severity, release, affected user, and business process.

## Business-Process KPIs

GermainUX can analyze business processes represented by browser activity, Windows application events, code transactions, logs, APIs, or synthetic scenarios.

| KPI | Description |
| - | - |
| Process Started | Number of process instances initiated |
| Process Completed | Number of successfully completed processes |
| Process Failed | Number of processes ending in failure |
| Process Abandoned | Number of processes started but not completed |
| Completion Rate | Percentage of started processes completed |
| Failure Rate | Percentage of process instances that failed |
| Abandonment Rate | Percentage of processes abandoned |
| Process Duration | End-to-end process execution time |
| Step Duration | Time spent on an individual step |
| Process Overrun | Time above the expected process duration |
| Lost Productivity | Time lost to errors, delays, repetition, or inefficient execution |

Examples include login, customer onboarding, order processing, case management, document handling, approvals, and custom employee workflows.

## API and Integration KPIs

For .NET APIs, services, and integrations, GermainUX can monitor:

* Request volume
* Response time
* HTTP status
* Success and failure rates
* Timeouts
* Retries

> [accordion] Show all 12
>
> * External-service duration
> * Database duration
> * Queue activity
> * Scheduled-job execution
> * Service availability
> * Exceptions and log errors

End-to-end correlation requires compatible timestamps and shared identifiers such as transaction, request, trace, or correlation IDs.

## Application and Infrastructure KPIs

The GermainUX Engine can collect operational KPIs from accessible application and infrastructure interfaces.

Common measurements include:

* Application and service availability
* Process state
* Process CPU and memory
* Host CPU and memory
* Disk and filesystem utilization
* Network availability and response time

> [accordion] Show all 11
>
> * Database response time
> * Connection utilization
> * Container or service health
> * Log error volume
> * Endpoint availability

The precise KPIs depend on the infrastructure and configured data sources.

## Synthetic-Monitoring KPIs

GermainUX RPA bots and automated HTTP actions can continuously validate important .NET applications and services.

| KPI | Description |
| - | - |
| Scenario Availability | Whether the complete synthetic scenario succeeded |
| Scenario Duration | End-to-end execution time |
| Step Duration | Time required for each scenario step |
| Validation Failure | Expected page, value, response, or outcome was not found |
| HTTP Availability | Whether an endpoint returned an acceptable response |
| HTTP Response Time | Time required for an endpoint to respond |
| Execution Error | Error encountered while running an automated test |

Synthetic scenarios can validate browser applications, supported Windows workflows, APIs, and business transactions.

## Automation KPIs

GermainUX records the outcome of configured monitoring and corrective actions, including:

* Alert volume
* SLA violation count
* Automated-action execution
* Automated-action success or failure
* Script execution
* HTTP action result

> [accordion] Show all 10
>
> * Recovery validation
> * Time to detect
> * Time to initiate remediation
> * Time to recover

Automated actions can include notifications, webhooks, HTTP requests, scripts, database operations, ticket creation, or approved service actions.

Corrective actions must be explicitly configured, authorized, and tested.

## Recommended Dashboard Measures

For each KPI, use the measures appropriate to the data:

* Count
* Unique users
* Affected sessions
* Average
* Median
* Percentiles

> [accordion] Show all 14
>
> * Minimum and maximum
> * Success and failure rates
> * Error count
> * Duration
> * Throughput
> * Trend compared with the previous period
> * Deviation from a baseline
> * Estimated lost productivity

Analyze percentiles and affected-user counts alongside averages. Averages alone can hide severe issues affecting a subset of users.

## Alerts and Reports

Configure alerts for conditions such as:

* Application or endpoint unavailable
* Increased exception or crash rate
* Application freezes
* Slow user

## Additional Resources

> [card] [Pivot and Measures for KPIs](https://docs.germainux.com/main/kpis.md)
>
> Read more

> [card] [Create your KPIs](https://docs.germainux.com/main/manage-kpis.md)
>
> Read more

## Get Help

> [card] [Contact GermainUX Support](https://docs.germainux.com/main/support.md)
>
> 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.

> [card] 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.