GermainUX-JS Profiler | Germain Documentation

⚙️ GermainUX JS Profiler

GermainUX JS Profiler captures advanced browser, JavaScript, and network diagnostics from real users. It helps development and support teams identify the front-end code responsible for slow interactions, errors, browser freezes, and other user-experience problems.

It provides capabilities similar to the Performance and Developer Tools available in a browser, but collects the evidence remotely and associates it with the affected user, session, application, and business workflow.

🕐 When to use JS Profiler

Use the JS Profiler when GermainUX Real User Monitoring identifies a problem that requires deeper technical evidence, such as:

	Symptom
1	Slow JavaScript execution
2	Long-running browser tasks
3	Browser freezes
4	JavaScript errors
5	Slow user interactions
6	Network-request failures
7	Excessive rendering or DOM activity
8	Front-end performance bottlenecks
9	Problems that cannot be reproduced by support or development teams

The JS Profiler complements Real User Monitoring. It is intended for deeper code-level analysis rather than continuous maximum-detail collection from every user.

🛰️ Capabilities

Depending on the configured profiling level, GermainUX can capture:

Capability
JavaScript function execution
Function duration
Exclusive and cumulative execution time
Long-running tasks
JavaScript errors and stack traces
Browser events
DOM activity
Network requests
Resource loading
User interactions
Page and session context
Application and browser details

This evidence can be correlated with:

Data type
User clicks
Page activity
Session Replay
HTTP requests
Application errors
Business workflows
Server-side transactions
Back-end code and dependencies

⚖️ Exclusive versus cumulative time

Measure	Meaning
Exclusive time	Time spent executing the function itself
Cumulative time	Total time spent in the function, including functions and operations it calls

A function with high exclusive time is directly consuming browser execution time. A function with low exclusive time but high cumulative time is typically invoking slower downstream functions, network activity, or other browser operations.

🔧 How it works

The JS Profiler is deployed as a browser extension. It collects detailed diagnostic information from monitored pages and sends it to GermainUX for centralized analysis.

The monitored page must also include or support the applicable GermainUX Real User Monitoring component. The RUM configuration supplies the application, user-session, and monitoring context used to organize the profiler data.

📋 Prerequisites

Before deploying the JS Profiler, confirm that:

Requirement
GermainUX Real User Monitoring is configured for the application.
The application and its pages are included in the monitoring scope.
The supported browser extension can be installed.
Enterprise browser policies permit the deployment.
The browser can reach Germain Enterprise.
Required URLs and ports are allowed.
Privacy and security requirements have been reviewed.
The profiling scope and target users are defined.

Some applications—such as Salesforce Lightning—may require a browser extension because application security boundaries prevent an injected component from accessing the complete top-level page context.

⬇️ Download

Download and install the GermainUX JS Profiler extension for the supported browser.

For enterprise deployments, distribute the extension using your organization’s browser-management platform, such as:

Method
Microsoft Group Policy
Microsoft Intune
Chrome Enterprise
Managed browser-extension policies
An approved internal extension store

Contact GermainUX Support for the current extension package, store location, and supported browser versions.

🛠️ Configure the application

Before enabling profiling:

Configure GermainUX Real User Monitoring for the target application.
Confirm that normal RUM data reaches GermainUX.
Define the profiling scope.
Select the users, applications, URLs, or conditions to profile.
Configure privacy exclusions.
Deploy the JS Profiler extension.
Restart or refresh the browser as required.
Generate a controlled test interaction.
Verify that profiler data appears in GermainUX.

See Deploy JavaScript Monitoring for the detailed deployment procedure.

🔍 Control profiling scope

Advanced JavaScript profiling can produce substantial data and browser overhead. Limit collection to the users, sessions, applications, or time periods required for the investigation.

Recommended approaches include:

Recommendation
Enable profiling for selected diagnostic users.
Limit profiling to affected applications or URLs.
Activate it only while investigating an issue.
Capture representative sessions rather than every session.
Disable profiling after sufficient evidence has been collected.
Expand the scope gradually after measuring overhead.

Real User Monitoring can remain enabled continuously while the deeper profiler is activated selectively.

🔒 Privacy and security

JavaScript profiling can capture detailed information about page activity, function execution, errors, URLs, and network requests.

Before deployment:

Action
Inform users according to your organization’s policies.
Exclude sensitive pages and fields.
Mask or anonymize personal information.
Avoid collecting authentication tokens or request payloads containing secrets.
Restrict profiler access to authorized teams.
Define data-retention requirements.
Validate monitoring against privacy and compliance policies.
Use HTTPS when sending data to GermainUX.

Review the profile after application changes because new pages, requests, or data fields may introduce additional sensitive information.

✅ Validate the deployment

Confirm that:

Check
The extension is installed and enabled.
Users cannot modify managed settings when the extension is centrally controlled.
The target application is recognized.
GermainUX RUM data is collected.
Profiler data is associated with the correct application and session.
JavaScript functions and errors appear.
Network and browser evidence is captured.
Session Replay and profiler evidence can be correlated.
Browser CPU, memory, and responsiveness remain acceptable.
Privacy exclusions operate as expected.

❗ Troubleshooting

❓ No profiler data appears

Verify:

Item
The JS Profiler extension is installed and enabled.
RUM is active on the page.
The application URL matches the configured monitoring scope.
The browser can reach Germain Enterprise.
Enterprise browser policy did not block or disable the extension.
The selected user or session is included in the profiling scope.
Privacy or exclusion rules are not removing all collected data.

🔧 The extension does not recognize the application

Check:

Item
Application URL patterns
Germain Enterprise URL
Monitoring-profile name
Browser-extension configuration
Environment selection
Whether the extension has refreshed its central configuration

📃 Browser performance degrades

Reduce:

Action
Profiling duration
Number of targeted users
Number of monitored pages
Function-level detail
Network or browser-event detail

Disable the profiler temporarily and confirm whether browser performance returns to normal.

📈 JavaScript details are incomplete

Some page contexts, cross-origin frames, browser security boundaries, or application frameworks may restrict access. Confirm that:

Check
The supported extension version is installed.
Required permissions are allowed.
Cross-origin frame support is configured where available.
The top-level application context is included.
The application uses a supported browser and framework version.

▶️ Recommended workflow

Use RUM, alerts, or Session Replay to identify an affected session.
Enable the JS Profiler for a controlled scope.
Reproduce or wait for another occurrence.
Review function, error, network, and browser evidence.
Identify the responsible code or dependency.
Implement the correction.
Validate the fix with RUM and profiling.
Disable unnecessary deep profiling.

Component: JS Profiler

Feature Availability: 2022.1 or later