> ## 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. # GermainUX Agent > GermainUX Agent enables Real User Monitoring, Session Replay, and code-level observability for supported native Windows applications. Components [`Agent`](https://docs.germainux.com/main/germainux-agent) Availability 2026.2 and later > [card] [Overview](#overview) > > Local monitoring connected to Enterprise > [card] [How It Works](#how-it-works) > > Architecture and runtime flow > [card] [Deployment Options](#deployment-options) > > Choose a deployment approach > [card] [Deployment and Configuration Guides](#deployment-and-configuration-guides) > > Links to setup guides **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: * 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 > [accordion] Show all 11 > > * 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: * 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: **1. GermainUX Agent connects to GermainUX Enterprise** **2. It retrieves the monitoring rules assigned to the machine and environment** **3. It detects configured application processes** **4. It starts the required monitoring components** **5. Monitoring data is sent to GermainUX Enterprise** **6. 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: * Users * Workstations * Servers * Applications * Environments ### Local Configuration Local monitoring configuration can be used for: * 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: * 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: **1. Review the requirements** **2. Install GermainUX Agent** **3. Connect the Agent to GermainUX Enterprise** **4. Configure the Windows applications to monitor** **5. Enable RUM Windows, Code Profiler, or both as required** **6. Start the monitored application** **7. Validate telemetry and Session Replay** **8. Roll out to additional users or systems** ## Deployment and Configuration Guides | Guide | Purpose | | - | - | | [**Setup & Configuration**](https://docs.germainux.com/main/setup-configuration.md) | Configure the Agent, monitored applications, and monitoring workflow | | [**Agent Installation**](https://docs.germainux.com/main/agent-installation.md) | Install, upgrade, repair, or uninstall GermainUX Agent | | [**Agent Settings**](https://docs.germainux.com/main/agent-settings-registry.md) | Configure Agent-level Windows settings | | [**Monitoring Config Reference**](https://docs.germainux.com/main/monitoring-config-reference.md) | Review the complete application-monitoring configuration | | [**Agent Troubleshooting**](https://docs.germainux.com/main/germainux-agent-troubleshooting.md) | Diagnose installation, startup, connectivity, configuration, and data-collection issues | ## Security and Data Privacy Before production deployment, define: * 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](https://docs.germainux.com/main/compliance-privacy-and-security.md) with representative application workflows before broad deployment. ## Validate After deployment, confirm that: * 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](https://docs.germainux.com/main/germainux-agent-troubleshooting.md) guide. ## Support For assistance installing, configuring, or troubleshooting GermainUX-Agent, contact [GermainUX Support](https://docs.germainux.com/main/support.md). ## 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.