⚙️ This guide
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 |
|
Always-running background process (tray icon). Watches for target application processes starting/stopping and manages the other two components. |
|
GermainUX-RUM Windows |
|
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. |
|
GermainUX-Code Profiler |
|
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 |
|---|---|
|
System requirements, running the installer, what gets installed, autostart, repair/uninstall |
|
|
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 |
|
|
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 |
|
|
Where the logs live, what they're named, and fixes for the most common setup problems |
🚀 Quick start
-
Run the installer appropriate for the target machine — see Installation for which of the two installers to use.
-
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. -
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.
-
To monitor an application without a server-side rule, add a local rule under the registry — see Agent Settings → Local Monitoring Rules.
-
Right-click the tray icon to check status, refresh configuration, or view the raw configuration currently applied to a monitored application.