Browser-monitoring components
Deploy independently or together
Required configuration
Minimum settings for most apps
Optional metadata
Extra application-specific context
Deployment and configuration
Install the browser agent
Overview
GermainUX includes preconfigured browser monitoring for user activity, Session Replay, performance, errors, network requests, browser freezes, and common user-experience friction. After deploying RUM JS, the RUM Extension, or the JS Profiler, most browser insights are automatically collected and analyzed. Additional configuration is required only when you need to customize the default behavior for a particular application or business requirement.Browser-monitoring components
These components can be deployed independently or together according to the required monitoring depth.
Preconfigured monitoring
Depending on the deployed component, GermainUX provides preconfigured monitoring for capabilities such as:
The exact monitoring available depends on the deployed component, browser capabilities, application architecture, and GermainUX version.
Required configuration
For most applications, configure only the following.Application and profile
1
Create or select the monitored application
2
Enter the application URL
3
Select the environment
4
Create or select the UX Monitoring Profile
5
Deploy RUM JS, the RUM Extension, or the JS Profiler
6
Confirm that browser telemetry reaches GermainUX
Security and privacy
Before production rollout, review and configure:
Privacy configuration must be validated across the application’s principal pages, forms, dialogs, routes, and frames.
Application identification
Confirm that GermainUX correctly identifies:Validation
1
Open the monitored application
2
Navigate through representative pages or routes
3
Perform several user actions
4
Execute representative network requests
5
Confirm that the session and browser facts appear in GermainUX
6
Open Session Replay when enabled
7
Confirm that sensitive information is protected
8
Verify that the expected performance, error, and network insights are available
Optional customization
Customize the preconfigured monitoring only when the default behavior does not meet the application’s requirements.Monitoring features
Optional application-specific insights
Additional configuration is appropriate when customers want GermainUX to understand application-specific business activity. Examples include:
Use the Browser Monitoring APIs and Custom Insights when these events are not already available through the preconfigured monitoring.
Optional metadata
GermainUX automatically provides standard browser and application context. Configure Metadata Extractors only when additional application-specific context is required, such as:
Collect only metadata that is necessary and authorized.
Optional KPI and SLA customization
GermainUX includes preconfigured browser KPIs, measures, pivots, and SLAs. Customize them only when you need to:
Review the available Browser Monitoring KPIs.
Deployment and configuration
- Review Browser Monitoring.
- Deploy GermainUX RUM JS, the GermainUX RUM Extension, or the GermainUX JS Profiler.
- Select the application, URL, environment, and UX Monitoring Profile.
- Review and validate Session Replay, privacy, consent, masking, sampling, access, and retention.
- Confirm that GermainUX’s preconfigured browser monitoring is collecting the expected data.
- Customize monitoring only when the application or business requirements differ from the preconfigured behavior.
- Review the available Browser Monitoring KPIs.
- Use the Browser Monitoring APIs for application-specific events and metadata.
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.