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

Select the Required Components

Combine components for correlation

Engine Deployment

Monitor out-of-process resources

Configure GermainUX

Review settings after install

Validate the Deployment

Trace a test transaction

​
Install and Configure Monitoring for .NET

​
Overview

GermainUX can monitor .NET applications across the user interface, application code, services, integrations, databases, and infrastructure. Supported monitoring scenarios include:
  • ASP.NET and ASP.NET Core web applications
  • .NET APIs and services
  • Native Windows applications built with .NET
  • Background services and scheduled processes
  • Application logs
  • Databases and integrations
  • Synthetic user transactions
Deploy only the GermainUX components required for your application and monitoring objectives.

​
Select the Required Components

A complete deployment can combine several components to correlate user experience, code execution, integrations, logs, and infrastructure behavior.

​
Prerequisites

Before deployment:
1

Identify the applications and environments to monitor

2

Confirm the .NET runtimes, operating systems, and deployment models

3

Obtain the required administrative or deployment permissions

4

Confirm network connectivity to the GermainUX environment

5

Define application and environment names

6

Configure credentials using an approved credential store

7

Determine privacy, masking, sampling, and retention requirements

8

Test the deployment in a nonproduction environment

The GermainUX services and monitored components must have synchronized system clocks for accurate correlation.

​
Browser-Based .NET Applications

Deploy GermainUX RUM JS for ASP.NET , ASP.NET Core, Blazor, or other compatible browser-based .NET applications.

​
Deployment

1

Go to Workspace > Settings > Wizards

2

Select the wizard for a browser or standard HTML application

3

Enter the application name, URL, environment, and privacy settings

4

Create or select a UX Monitoring Profile

5

Generate the RUM JS loader

6

Add it to the common application layout or page template

7

Deploy the application

8

Confirm that browser sessions reach GermainUX

Load RUM JS early enough to capture page initialization and subsequent user activity. Ensure that the application’s Content Security Policy and network configuration permit communication with GermainUX.

​
Available monitoring

Depending on configuration, RUM JS can capture:
  • User sessions
  • Pages and navigation
  • Clicks and user actions
  • Page and action response times
  • Browser and JavaScript errors
  • Network requests
  • Business-process activity
  • User feedback
  • Session Replay
For applications using frames, RUM JS must run in each browser context that needs to be monitored. Cross-origin restrictions can prevent a script in one frame from accessing another.

​
Native Windows .NET Applications

Deploy GermainUX RUM for Windows to monitor supported .NET desktop applications.

​
Deployment

1

Obtain the GermainUX Windows monitoring package

2

Configure the GermainUX environment URL

3

Define the applications and executable processes to monitor

4

Configure user identification and environment attributes

5

Apply masking, exclusion, and recording rules

6

Deploy the package to a test device

7

Start the monitored application and complete a representative workflow

8

Confirm that user activity and Session Replay appear in GermainUX

9

Distribute the configuration through the organization’s approved software-management platform

Windows monitoring can capture configured application lifecycle, window, control, mouse, keyboard, search, freeze, crash, and workflow activity. The information available depends on the application framework, control implementation, permissions, and monitoring configuration.

​
.NET Code Profiling

Deploy the GermainUX Code Profiler to monitor supported .NET application transactions and method execution.

​
Deployment

1

Identify the .NET processes to profile

2

Confirm that the application runtime and hosting model are supported

3

Install the Code Profiler on the application host or container

4

Configure the GermainUX service URL, application, environment, and process scope

5

Select the transactions, namespaces, assemblies, or methods to include or exclude

6

Restart the application or service if required to attach the profiler

7

Execute representative transactions

8

Confirm that profiling telemetry reaches GermainUX

The Code Profiler can provide visibility into:
  • Transaction duration
  • Method execution
  • Exclusive and cumulative time
  • Invocation count
  • Exceptions
  • Database operations
  • External-service calls
  • Slow code paths
Limit profiling to the code and transactions required for analysis. Broad profiling can generate unnecessary overhead and data volume.

​
Engine Deployment

Deploy the GermainUX Engine to monitor application resources that are accessible outside the .NET process. The Engine can support:
  • Application and service availability
  • API and HTTP monitoring
  • Log and file monitoring
  • Windows services and processes
  • Hosts and infrastructure
  • Databases
  • Scheduled jobs
  • Integrations
  • Synthetic transactions
  • Alerts, reports, and automated actions

​
Deployment

1

Install the GermainUX Engine on a suitable host

2

Register it with the GermainUX environment

3

Configure the Engine name and operating settings

4

Create the required credentials and data sources

5

Run the appropriate application, host, database, file, or HTTP wizard

6

Assign the monitor to the Engine

7

Configure its schedule

8

Confirm that the component is running and collecting data

The Engine requires network access to both GermainUX and the monitored resources.

​
Synthetic Monitoring

Use the GermainUX RPA Bot Recorder to create synthetic scenarios for browser-based or supported Windows .NET applications. Examples include:
  • Login
  • Search
  • Record creation
  • Form submission
  • Checkout
  • Approval
  • API validation
  • Custom business workflows
After recording a scenario:
1

Add validation points

2

Assign the scenario to a GermainUX Engine

3

Configure its schedule and timeout

4

Define alert conditions

5

Use dedicated test credentials and controlled test data

6

Test the scenario before enabling it in production

​
Configure GermainUX

After deploying the required components, review the following configuration.

​
Data sources and applications

Go to Workspace > Settings and confirm that:
  • The .NET application is enabled.
  • Required hosts, URLs, files, databases, and services are configured.
  • Credentials use the minimum required permissions.
  • Application and environment names are consistent across components.

​
Analytics

Go to Workspace > Analytics to configure or review:
  • KPIs
  • UX Monitoring Profiles
  • Business Processes
  • Categorization
  • Correlation
  • Data Privacy
  • Rules
  • SLAs
Correlation between browser, Windows, code, log, and infrastructure telemetry requires consistent identifiers and timestamps.

​
Automation

Configure:
  • Alerts
  • Scheduled reports
  • HTTP actions and webhooks
  • Approved scripts
  • Database actions
  • Ticketing integrations
  • Corrective actions
Automated actions must be explicitly authorized, tested, and restricted to approved systems.

​
Dashboards

Go to Workspace > Dashboards > All to locate the available .NET, application, user-experience, business-process, and infrastructure dashboards or create a custom dashboard.

​
Privacy and Security

Before production rollout:
  • Mask passwords and sensitive input.
  • Exclude authentication tokens and confidential content.
  • Limit captured user identifiers.
  • Configure Session Replay exclusions.
  • Restrict access to code, user, and replay data.
  • Secure profiler and Engine credentials.
  • Define appropriate retention periods.
  • Review all monitoring against organizational requirements.

​
Validate the Deployment

Complete a representative transaction and verify that:
  • The application is identified correctly.
  • The correct environment is assigned.
  • User sessions and replays are available where enabled.
  • Code transactions and exceptions are captured where profiling is enabled.
  • Logs, services, APIs, and infrastructure metrics reach GermainUX.
  • Related telemetry can be correlated.
  • Sensitive information is masked or excluded.
  • Dashboards display the expected KPIs.
  • Alerts and reports reach the intended recipients.

​
Additional Resources

Troubleshooting Tips

Read more

Management

More Management Features

​
Get Help

Contact GermainUX Support

The Germain Team can help you set this up.

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