⚙️ GermainUX Agent
GermainUX Agent enables Real User Monitoring, Session Replay, and code-level observability for supported native Windows applications.
Installed on a Windows workstation or server, GermainUX Agent detects configured applications when they start and automatically activates the required monitoring components. No changes to the monitored application's source code are required.
👀 Overview
GermainUX Agent runs locally on Windows and connects to GermainUX Enterprise to retrieve the monitoring configuration assigned to the machine and application.
Depending on the configuration, it can monitor:
|
Feature |
|---|
|
Application launches, exits, freezes, and crashes |
|
Windows, screens, dialogs, and user workflows |
|
Mouse, keyboard, and navigation activity |
|
Application responsiveness |
|
CPU and memory utilization |
|
.NET runtime health |
|
Garbage collection |
|
Unhandled exceptions |
|
Outbound HTTP requests |
|
User activity and productivity |
|
Session Replay |
Collected telemetry is securely sent to GermainUX Enterprise for analysis, dashboards, alerts, reports, correlation, and Session Replay.
📅 When to Use GermainUX Agent
Use GermainUX Agent when monitoring supported:
|
Supported Type |
|---|
|
Native Windows applications |
|
.NET applications |
|
C# applications |
|
C++ applications |
|
Other supported Windows application technologies |
GermainUX Agent is also required when GermainUX RUM Windows or the supported Windows Code Profiler must execute locally on the user's workstation or application server.
📦 Components
The standard 64-bit GermainUX Agent installation includes:
|
Component |
Purpose |
|---|---|
|
GermainUX Agent |
Detects configured applications, retrieves monitoring rules, and manages local monitoring components |
|
GermainUX RUM Windows |
Captures native Windows user activity, responsiveness, workflows, and Session Replay |
|
GermainUX Code Profiler |
Provides runtime and code-level observability for supported .NET applications |
The Agent activates RUM Windows, Code Profiler, or both according to the monitoring configuration associated with each application.
🔗 How It Works
A typical architecture is:
Native Windows Application → GermainUX Agent → GermainUX Enterprise
At runtime:
-
GermainUX Agent connects to GermainUX Enterprise.
-
It retrieves the monitoring rules assigned to the machine and environment.
-
It detects configured application processes.
-
It starts the required monitoring components.
-
Monitoring data is sent to GermainUX Enterprise.
-
GermainUX correlates the resulting user, application, performance, and technical telemetry.
Monitoring can be centrally managed from GermainUX Enterprise or, when required, configured locally.
💻 Deployment Options
🌐 Centrally Managed
Recommended for production deployments.
Monitoring rules are maintained centrally in GermainUX Enterprise and automatically retrieved by the Agent.
This allows monitoring to be managed consistently across:
|
Scope |
|---|
|
Users |
|
Workstations |
|
Servers |
|
Applications |
|
Environments |
🔧 Local Configuration
Local monitoring configuration can be used for:
|
Use Case |
|---|
|
Initial testing |
|
Diagnostics |
|
Offline environments |
|
Individually managed machines |
|
Environments where central configuration cannot be retrieved |
Detailed local settings are documented separately.
📋 Requirements
At a high level, GermainUX Agent requires:
|
Requirement |
|---|
|
A supported 64-bit Windows operating system |
|
Administrator privileges for installation |
|
An authorized Windows account for running the Agent |
|
Required Microsoft runtime prerequisites |
|
Network access to GermainUX Enterprise |
|
Authorization to monitor the selected applications and users |
Review the installation guide for the complete requirements and installer-selection details.
🚀 Deployment Overview
A standard deployment consists of:
-
Review the requirements.
-
Install GermainUX Agent.
-
Connect the Agent to GermainUX Enterprise.
-
Configure the Windows applications to monitor.
-
Enable RUM Windows, Code Profiler, or both as required.
-
Start the monitored application.
-
Validate telemetry and Session Replay.
-
Roll out to additional users or systems.
📖 Deployment and Configuration Guides
|
Guide |
Purpose |
|---|---|
|
Configure the Agent, monitored applications, and monitoring workflow |
|
|
Install, upgrade, repair, or uninstall GermainUX Agent |
|
|
Configure Agent-level Windows settings |
|
|
Review the complete application-monitoring configuration |
|
|
Diagnose installation, startup, connectivity, configuration, and data-collection issues |
🔒 Security and Data Privacy
Before production deployment, define:
|
Item |
|---|
|
Applications and processes that may be monitored |
|
Users and environments that may be monitored |
|
User interactions that may be captured |
|
Windows or controls that must be excluded |
|
Sensitive values that must be masked |
|
Whether Session Replay may be enabled |
|
Who may access collected user-level data |
|
Appropriate retention policies |
Validate privacy controls with representative application workflows before broad deployment.
✅ Validate
After deployment, confirm that:
|
Check |
|---|
|
GermainUX Agent is running. |
|
It connects to GermainUX Enterprise. |
|
The expected monitoring configuration is loaded. |
|
The monitored application is detected. |
|
RUM Windows and/or Code Profiler starts when required. |
|
Monitoring data appears in GermainUX. |
|
Session Replay works when enabled. |
|
Sensitive information is excluded or masked correctly. |
For detailed diagnostics, use the Agent Troubleshooting guide.
📞 Support
For assistance installing, configuring, or troubleshooting GermainUX-Agent, contact GermainUX Support.
Component: Agent
Feature Availability: 2026.2 and later