> ## 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 of Browser

> GermainUX provides three components for monitoring browser-based applications. Choose the one that fits your application.

Components
[`JS Profiler`](/main/germain-ux-js-profiler)
[`RUM JS`](/main/germain-ux-rum-js)
[`RUM Extension`](/main/germain-ux-rum-extension)

Availability
2022.1 or later

> **[Deploy Browser Monitoring](#deploy-browser-monitoring)**
>
> Three independent components

> **[Deploy the JS Profiler](#deploy-the-js-profiler)**
>
> Profile JavaScript execution

## Deploy Browser Monitoring

GermainUX provides three components for monitoring browser-based applications:

| Component | Primary purpose | Recommended use |
| - | - | - |
| [GermainUX RUM JS](/main/germain-ux-rum-js.md) | Continuously monitor real-user activity, performance, errors, network requests, Session Replay, heatmaps, and business events | Applications where the GermainUX monitoring script can be deployed |
| [GermainUX RUM Extension](/main/germain-ux-rum-extension.md) | Provide Real User Monitoring and Session Replay when JavaScript injection is unavailable or browser-level access is required | Third-party or SaaS applications, root-page monitoring, managed browser deployments, and supported cross-origin frames |
| [GermainUX JS Profiler](/main/germain-ux-js-profiler.md) | Continuously profile and analyze JavaScript execution, browser activity, and performance | Applications requiring deeper JavaScript troubleshooting and function-level performance analysis |

The components can be deployed independently or together, depending on the required monitoring coverage.

### Choose the deployment method

| Requirement | Recommended component |
| - | - |
| Monitor real users in an application you control | RUM JS |
| Record and replay user sessions | RUM JS or RUM Extension |
| Monitor a third-party application that cannot load RUM JS | RUM Extension |
| Monitor the root browser context of a SaaS application | RUM Extension |
| Deploy monitoring centrally to managed browsers | RUM Extension |
| Profile JavaScript execution continuously | JS Profiler |
| Identify slow or excessively executed JavaScript functions | JS Profiler |
| Diagnose browser-side code responsible for slow interactions | JS Profiler |
| Combine user experience with function-level JavaScript evidence | RUM JS or RUM Extension with JS Profiler |
| Test critical browser workflows proactively | RPA Bot Recorder and Engine |

Also update the deployment architecture table:

| Component | Where it runs | Purpose |
| - | - | - |
| RUM JS | Monitored web application | Captures browser activity, performance, errors, network requests, Session Replay, and business events |
| RUM Extension | User’s Chrome, Edge, or Firefox browser | Provides browser monitoring when script deployment is unavailable or browser-level access is required |
| JS Profiler | Supported browser | Continuously profiles JavaScript execution and identifies function-level performance bottlenecks |
| Germain Enterprise | GermainUX cloud or on-premises environment | Receives, processes, stores, and analyzes browser telemetry |
| RPA Bot Recorder | Scenario-authoring browser | Records synthetic user workflows |
| GermainUX Engine | Synthetic or backend environment | Executes synthetic scenarios and monitors supporting systems |

And replace the previous **Deploy the JS Profiler** section with:

## Deploy the JS Profiler

Use the [GermainUX JS Profiler](/main/germain-ux-js-profiler.md) to continuously monitor and analyze JavaScript execution in a supported browser.

The JS Profiler can help identify:

| Issue | Details |
| - | - |
| Slow JavaScript functions | Slow JavaScript functions |
| Functions consuming excessive execution time | Functions consuming excessive execution time |
| Repeated or inefficient function calls | Repeated or inefficient function calls |
| JavaScript activity associated with slow user interactions | JavaScript activity associated with slow user interactions |
| Browser-side code contributing to freezes or poor responsiveness | Browser-side code contributing to freezes or poor responsiveness |
| Performance differences across pages, workflows, and application versions | Performance differences across pages, workflows, and application versions |

### Deployment

1. Download the GermainUX JS Profiler extension for a supported browser.
2. Install it manually for selected users or deploy it through an approved enterprise browser-management mechanism.
3. Configure the GermainUX environment.
4. Configure the websites and applications to be monitored.
5. Associate the deployment with the corresponding GermainUX application and profile.
6. Enable the required JavaScript profiling capabilities.
7. Open the monitored application and execute representative workflows.
8. Confirm that JavaScript profiling data is received by GermainUX.
9. Validate browser performance and data volume before expanding the deployment.

The JS Profiler can operate as a browser-monitoring component in its own right. Deploy it together with RUM JS or the RUM Extension when user activity, Session Replay, and function-level JavaScript evidence must be analyzed in the same operational context.

Finally, update the component summary to:

## Get Help

> **[Contact GermainUX Support](/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.