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

# Deploy Monitoring or Automation for Windows Application

> The GermainUX Agent is a set of Windows components that observe a target app and send its activity to GermainUX as facts and optional replay data.

Components
[`Engine`](https://docs.germainux.com/main/germain-ux-engine)
[`JS Profiler`](https://docs.germainux.com/main/germain-ux-js-profiler)
[`Mobile App`](https://docs.germainux.com/main/germain-ux-mobile-app)
[`RPA Bot Recorder`](https://docs.germainux.com/main/germain-ux-rpa-bot-recorder)
[`RUM Windows`](https://docs.germainux.com/main/germainux-rum-windows)
[`Agent`](https://docs.germainux.com/main/germainux-agent)

Availability
2026.2

> **[About the Agent](#what-the-germainux-agent-is)**
>
> Agent role and capabilities

> **[Documents in this guide](#documents-in-this-guide)**
>
> Related guides and reference

> **[Quick start](#quick-start)**
>
> Install and start the Agent

## Overview

> [!NOTE]
>
> This guide covers installing, configuring, and troubleshooting the **GermainUX - Agent** on an end-user or server machine. It is written for IT administrators and support staff deploying the agent, not for developers working on its source.

## What the GermainUX - Agent is

The GermainUX - Agent is a set of Windows components that observe a target application (its windows, controls, clicks, HTTP calls, and .NET runtime health) and send that activity to GermainUX as monitoring facts and, optionally, session replay data. It has three parts, installed together:

| Component | File | Role |
| - | - | - |
| GermainUX - Agent | `GermainUXAgent.exe` | Always-running background process (tray icon). Watches for target application processes starting/stopping and manages the other two components. |
| GermainUX - RUM Windows | `GermainUXRumWindows.exe` | Started automatically by the Agent, one per monitored application. Reads the target application's UI (window titles, controls, clicks) and reports UI activity and, if enabled, session replay. |
| Code Profiler | `GermainUXCodeProfiler.dll` | Loaded directly into a monitored .NET application to report CPU usage, garbage collection, unhandled exceptions, and outbound HTTP calls from inside the process. |

None of this requires changes to the applications being monitored — the Agent attaches to them automatically based on rules it downloads from your GermainUX server (or, for offline/manual setups, rules stored locally on the machine).

## Documents in this guide

| Document | Covers |
| - | - |
| [Installation](https://docs.germainux.com/main/germainux-agent-installation.md) | System requirements, running the installer, what gets installed, autostart, repair/uninstall |
| [Agent Settings](https://docs.germainux.com/main/germainux-agent-settings-registry.md) | The one-time, per-machine registry settings that control the Agent itself (server URL, log levels, polling, hooks), and how to add monitoring rules manually without a server |
| [Monitoring Configuration Reference](https://docs.germainux.com/main/configure-monitoring-or-automation-for-windows-application.md) | The full JSON schema for a monitoring rule — every feature the Agent/Worker/Profiler can be told to collect, and how to author or edit one |
| [Troubleshooting](https://docs.germainux.com/main/germainux-agent-troubleshooting.md) | Where the logs live, what they're named, and fixes for the most common setup problems |

## Quick start

1. Run the installer appropriate for the target machine — see [Installation](https://docs.germainux.com/main/germainux-agent-installation.md) for which of the two installers to use.
2. During install, enter your organization's **GermainUX URL** when prompted (defaults to `https://server.cloud.germainux.com`). This is the only setting the installer asks for.
3. The Agent starts automatically (elevated, via a scheduled task) the next time an administrator logs on, and polls the GermainUX server for monitoring rules that match applications running on the machine.
4. To monitor an application without a server-side rule, add a local rule under the registry — see [Agent Settings → Local Monitoring Rules](https://docs.germainux.com/main/germainux-agent-settings-registry.md).
5. Right-click the tray icon to check status, refresh configuration, or view the raw configuration currently applied to a monitored application.

## Additional Resources

> **[Troubleshooting Tips](https://docs.germainux.com/main/germain-enterprise-troubleshooting.md)**
>
> Read more

> **[Management](https://docs.germainux.com/main/management.md)**
>
> More Management Features

## Get Help

> **[Contact GermainUX Support](https://docs.germainux.com/main/support.md)**
>
> 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.