Skip to main content
ComponentsAgentEngineJS ProfilerMobile AppRPA Bot RecorderRUM Windows
Availability2026.2 or later

Browser User-Experience KPIs

Segment by page and device

Business-Process KPIs

Measure processes across channels

Synthetic-Monitoring KPIs

Bots validating key applications

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: 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
  • 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: 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
  • 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. 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
  • 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
  • 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. 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
  • 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. For each KPI, use the measures appropriate to the data:
  • Count
  • Unique users
  • Affected sessions
  • Average
  • Median
  • Percentiles
  • 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

Pivot and Measures for KPIs

Read more

Create your KPIs

Read more

​
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.