Skip to main content
ComponentsJS ProfilerRUM JSRUM Extension
Availability2017.1 or later
GermainUX JS Profiler GermainUX JS Profiler captures advanced JavaScript, browser, and network diagnostics from real users. It complements GermainUX Real User Monitoring by providing deeper technical evidence when a front-end issue requires code-level investigation.

When to Use JS Profiler

Find slow JavaScript execution

Requirements

Browser and deployment prerequisites

Control Profiling Scope

Limit overhead and data volume

Support

Contact support for help

​
Overview

JS Profiler provides detailed diagnostic information correlated with: It is best used for targeted diagnostics rather than continuous maximum-detail profiling for every user.

​
When to Use JS Profiler

Use JS Profiler to investigate:
  • Slow JavaScript
  • Long-running browser tasks
  • Browser freezes
  • JavaScript errors
  • Slow interactions
  • Network failures
  • Excessive rendering or DOM activity
  • Front-end performance bottlenecks
  • Issues that development or support teams cannot reproduce

​
Capabilities

Depending on configuration, GermainUX can capture:
  • JavaScript function execution
  • Function duration
  • Exclusive and cumulative time
  • Long-running tasks
  • JavaScript errors
  • Stack traces
  • Browser events
  • DOM activity
  • Network requests
  • Resource loading
  • User interactions
  • Page and session context

​
Architecture

Web Application → GermainUX Real User Monitoring + JS Profiler → GermainUX Enterprise GermainUX Real User Monitoring provides the application and session context used to organize profiler data.

​
Requirements

Before deployment:
  • Configure GermainUX Real User Monitoring.
  • Confirm normal RUM telemetry.
  • Confirm supported browser-extension deployment.
  • Define applications and URLs to profile.
  • Confirm connectivity to GermainUX.
  • Review privacy requirements.

​
Deployment Overview

1

Configure Real User Monitoring

2

Confirm RUM telemetry

3

Define profiling scope

4

Configure privacy exclusions

5

Install or centrally deploy JS Profiler

6

Generate representative interactions

7

Verify profiler telemetry in GermainUX

​
Control Profiling Scope

Advanced profiling can increase browser overhead and data volume. Prefer to:
  • Target diagnostic users.
  • Limit profiling to affected applications or URLs.
  • Enable deep profiling during investigations.
  • Capture representative sessions.
  • Disable unnecessary deep profiling after collecting sufficient evidence.

​
Security and Data Privacy

Before deployment:
  • Exclude sensitive pages and fields.
  • Mask or anonymize personal information.
  • Avoid capturing secrets or authentication tokens.
  • Restrict profiler access.
  • Define appropriate retention.

​
Validate

Confirm:
  • JS Profiler is installed and enabled.
  • The application is recognized.
  • RUM data is present.
  • Profiler telemetry is associated with the correct session.
  • JavaScript functions and errors appear.
  • Network and browser evidence is captured.
  • Browser performance remains acceptable.
  • Privacy exclusions operate correctly.
GermainUX JS Profiler GermainUX RUM JS GermainUX RUM Extension

​
Support

For assistance installing, configuring, or troubleshooting GermainUX-Agent, contact GermainUX Support.

​
Get Help

Contact GermainUX Support

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