⚙️ GermainUX-Agent Setup and Configuration
📖 Overview
This guide explains how to install, configure, validate, and troubleshoot GermainUX-Agent on a Windows workstation or server.
It is intended for administrators responsible for deploying GermainUX real-user monitoring, Session Replay, and code-level observability for native Windows applications.
No changes to the monitored application’s source code are required. GermainUX-Agent detects configured applications and automatically activates the required monitoring components.
🗂️ Architecture
The standard GermainUX-Agent installation contains three coordinated components:
|
Component |
File |
Purpose |
|---|---|---|
|
GermainUX-Agent |
|
Runs in the background, detects configured application processes, retrieves monitoring rules, and manages the other components. |
|
GermainUX-RUM Windows |
|
Captures application windows, controls, clicks, user activity, responsiveness, workflow telemetry, and—when enabled—Session Replay. |
|
GermainUX-Code Profiler |
|
Attaches to supported .NET applications to capture CPU activity, garbage collection, exceptions, runtime health, and outbound HTTP requests. |
The components are installed together and must remain in the same installation directory.
⚙️ How It Works
-
GermainUX-Agent starts automatically when an authorized Windows administrator signs in.
-
It connects to the configured GermainUX Enterprise environment.
-
It retrieves the monitoring rules assigned to the machine and environment.
-
It watches for the executable defined in each rule.
-
When a monitored application starts, the Agent activates:
-
RUM Windows for user-interface monitoring and Session Replay
-
Code Profiler for supported .NET runtime monitoring
-
Both components when user experience and code-level observability are required
-
-
The collected telemetry is transmitted to GermainUX Enterprise for analysis, dashboards, alerting, reporting, correlation, and Session Replay.
📋 Before You Begin
Confirm that the target machine meets these requirements:
|
Requirement |
|---|
|
Supported 64-bit Windows operating system |
|
Administrator privileges for installation |
|
A local administrator account for running the Agent |
|
Microsoft Visual C++ 2015–2022 Redistributable |
|
Network access to the cloud or on-premise GermainUX Enterprise environment |
|
Authorization to monitor the selected applications and users |
|
An existing or planned monitoring configuration for each target application |
The Agent must run with elevated privileges to detect application processes. It also runs within the interactive Windows session to capture authorized user-interface activity.
📦 Select the Appropriate Installer
Two packages are available:
|
Installer |
Use |
|---|---|
|
Setup64 |
Standard installation for almost every deployment. Includes GermainUX-Agent, RUM Windows, the 64-bit Code Profiler, and diagnostic utilities. |
|
Setup x86 |
Optional package for CLR-level profiling of 32-bit .NET applications. It does not install GermainUX-Agent or RUM Windows. |
Install Setup64 unless you specifically need to profile a 32-bit .NET application or GermainUX Support has instructed you otherwise.
Both packages can be installed on the same machine when monitoring both 64-bit and 32-bit applications.
💻 Install GermainUX-Agent
-
Download the appropriate installer.
-
Run
Setup64.msiwith administrator privileges. -
Enter the base URL of your GermainUX Enterprise environment.
-
Accept the default installation folder or select another location.
-
Complete the installation.
-
Sign out and sign back in using an authorized local administrator account.
A Windows restart is not normally required.
The Agent does not start immediately after installation. A Windows Scheduled Task launches it with elevated privileges the next time an authorized administrator signs in.
See Agent Installation for detailed installation, upgrade, repair, and uninstallation instructions.
🔗 Configure the GermainUX Connection
The installer stores the GermainUX Enterprise URL in the following machine-wide Windows Registry location:
HKLM\SOFTWARE\Germain Software\Germain Agent
The URL may point to either:
|
Type |
Details |
|---|---|
|
A GermainUX Cloud environment |
|
|
An on-premise GermainUX Enterprise environment |
|
|
A GermainUX Enterprise environment hosted within your private cloud |
|
Additional registry settings control the environment, log levels, polling frequency, mouse and keyboard hooks, worker behavior, and local monitoring rules.
Registry changes take effect only after the affected process is restarted.
See Agent Settings for the complete configuration reference.
🔧 Configure Application Monitoring
🌐 Centrally Managed Configuration
For production deployments, configure the monitored applications and their rules centrally in GermainUX Enterprise.
The Agent periodically retrieves:
|
Item |
Details |
|---|---|
|
The applications it should monitor |
|
|
The target executable for each application |
|
|
The environment and monitoring profile |
|
|
Whether RUM Windows is enabled |
|
|
Whether Code Profiler attachment is enabled |
|
|
The user activity and performance telemetry to collect |
|
|
Session Replay settings |
|
|
Data-buffering and transmission settings |
|
|
Privacy, exclusion, and masking rules |
|
Central configuration makes it possible to manage monitoring consistently across multiple users, machines, applications, and environments.
🏠 Local Configuration
Monitoring rules can also be defined locally when central configuration is unavailable or inappropriate.
Typical uses include:
|
Use |
Details |
|---|---|
|
Initial testing |
|
|
Offline monitoring |
|
|
Diagnostics |
|
|
One-time deployments |
|
|
Individually managed machines |
|
A local rule is defined under:
HKLM\SOFTWARE\Germain Software\Germain Agent\Targets\{executableName.exe}
The rule references a local JSON configuration file containing the monitoring settings.
A local rule takes precedence over a centrally provided rule for the same executable.
See:
🏁 Validate the Deployment
After signing in and starting the monitored application:
-
Confirm that the GermainUX-Agent icon appears in the Windows system tray.
-
Right-click the icon and verify that Monitoring Enabled is selected.
-
Select Refresh Config to retrieve the latest configuration immediately.
-
Open Configurations and confirm that the expected application rule is listed.
-
Review the resolved configuration to verify:
-
Start or restart the monitored application.
-
Confirm that telemetry appears in GermainUX Workspace.
-
If enabled, validate that Session Replay is being generated.
-
Confirm that sensitive data is excluded, masked, or anonymized as expected.
|
Item |
Details |
|---|---|
|
Target executable |
|
|
Application and environment |
|
|
RUM Windows status |
|
|
Code Profiler status |
|
|
Monitoring profile |
|
|
Applied configuration |
|
📌 System-Tray Controls
Right-click the GermainUX-Agent tray icon to access the following controls:
|
Option |
Purpose |
|---|---|
|
Monitoring Enabled |
Pauses or resumes all monitoring without stopping the Agent. |
|
Refresh Config |
Immediately retrieves the latest rules from GermainUX Enterprise. |
|
Configurations |
Displays the remote and local rules currently available to the Agent and their resolved configuration. |
|
About |
Displays Agent version information. |
|
Exit |
Stops GermainUX-Agent and its managed monitoring activity. |
The Configurations view is the fastest way to confirm which settings are actually being applied to a monitored application.
Troubleshooting
If the Agent does not start, retrieve its configuration, detect an application, or send telemetry:
-
Confirm that the signed-in user is a local administrator.
-
Verify that the GermainUX-Agent tray icon is present.
-
Confirm that the GermainUX Enterprise URL is correct.
-
Validate network and proxy access to the GermainUX environment.
-
Select Refresh Config from the tray menu.
-
Confirm that the expected monitoring rule is listed.
-
Verify that the rule uses the correct executable name.
-
Restart the monitored application after configuration changes.
-
Review the Agent, RUM Windows, and Code Profiler logs.
-
Temporarily increase the appropriate log level when additional diagnostic detail is required.
See Agent Troubleshooting for log locations and solutions to common deployment problems.
🔗 Related Documentation
|
Guide |
Description |
|---|---|
|
System requirements, installer selection, installation, automatic startup, upgrades, repair, and uninstallation |
|
|
GermainUX URL, environment, logging, polling, hooks, worker behavior, and local monitoring rules |
|
|
Complete JSON reference for configuring application, UI, performance, HTTP, resource, and Session Replay monitoring |
|
|
Log files and solutions to common startup, configuration, connectivity, and data-collection problems |
Service: Management
Feature Availability: 2014.1 or later