Configuring GermainUX Monitoring for MarkoJS Applications: Session Replay, Errors, and Performance Management

Configure Monitoring for MarkoJS

Configure GermainUX monitoring for your MarkoJS application to control Session Replay, errors, performance, privacy, exclusions, and advanced JavaScript monitoring.

This guide assumes that GermainUX RUM JS has already been deployed on the MarkoJS application.

⚙️ Access the UX Monitoring Profile

Go to:

Germain Workspace → Settings → Analytics → UX Monitoring Profiles

Select the UX Monitoring Profile associated with your MarkoJS application.

The UX Monitoring Profile controls how GermainUX monitors users and their experience with the application.

🎥 Configure Session Replay

Session Replay is enabled by default for each UX Monitoring Profile.

From the MarkoJS UX Monitoring Profile, enable or disable:

Session Replay Monitoring

This setting controls Session Replay for the selected MarkoJS application.

Additional global Session Replay settings are available under:

Germain Workspace → Settings → System → UX and Session Replay Settings

These settings include the session timeout and other Session Replay behavior.

🚨 Configure JavaScript & Console Error Monitoring

GermainUX RUM JS automatically captures JavaScript window errors and browser console errors.

By default, window errors and console.error events are monitored.

Advanced configuration can be used to control which console methods are captured, including:

• error

• warn

• info

• log

You can also configure the maximum amount of console content collected for each event.

This is useful for reducing unnecessary data while retaining the information required to troubleshoot errors affecting MarkoJS users.

🧊 Configure Browser Freeze & Long Task Detection

GermainUX RUM JS can detect long-running JavaScript tasks that block the browser's main UI thread.

These events can indicate:

• Browser freezes

• Slow interaction response

• Delayed user actions

• Poor scrolling or animation performance

• Heavy JavaScript processing

Long Task monitoring is enabled by default.

The duration threshold can be customized in the UX Monitoring Profile's Init Script when the default threshold is not appropriate for your application.

🚀 Configure Advanced JavaScript Profiling

Enable JavaScript Profiling Monitoring when deeper JavaScript performance diagnostics are required.

Go to:

Germain Workspace → Settings → Analytics → UX Monitoring Profiles → [MarkoJS Profile]

Select:

JavaScript Profiling Monitoring

JavaScript profiling can provide deeper visibility into JavaScript execution and help identify expensive or slow-running code.

Profiling can be configured using supported browser mechanisms, including the JavaScript Self-Profiling API or GermainUX browser profiling capabilities.

Advanced settings can control:

• Profiling duration

• Sampling interval

• Sample capacity

• Minimum function/stack hits

• Profiling when the page becomes ready

• Included users

• Excluded users

Enable deep JavaScript profiling only where the additional diagnostic detail is required.

🤖 Exclude Bots & Crawlers

Bots and crawlers can be excluded so their activity does not affect MarkoJS user-experience analytics or consume unnecessary monitoring resources.

Go to:

Germain Workspace → Settings → Analytics → UX Monitoring Profiles → [MarkoJS Profile]

Configure:

Excluded User Agents

Default bot and crawler exclusions can also be enabled during the initial RUM JS deployment.

🌐 Include or Exclude IP Addresses

Control which users are monitored based on their IP address.

Configure:

• Excluded IP Ranges — prevent selected IP addresses or ranges from being monitored.

• Included IP Ranges — restrict monitoring to selected IP addresses or ranges.

This can be useful for excluding:

• Internal users

• Test environments

• Synthetic monitoring

• Development activity

or for limiting monitoring to a specific population during testing or rollout.

👤 Exclude Users

Specific usernames can be excluded from monitoring.

Go to:

Germain Workspace → Settings → Analytics → UX Monitoring Profiles → [MarkoJS Profile]

Configure:

Excluded Usernames

This can be useful for excluding:

• Test accounts

• Automated users

• Administrative accounts

• Synthetic users

The MarkoJS application must expose the username to GermainUX before username-based exclusions can be applied.

🤖 Exclude Headless Browsers

Headless browsers can be excluded from Real User Monitoring and Session Replay.

Enable:

Exclude Headless Browsers

This prevents automated browser activity from being included in real-user analytics when it should be analyzed separately.

🔎 Configure Phrases of Interest

Use Phrases of Interest to detect important text displayed within the MarkoJS application.

Examples include:

• Error messages

• Warnings

• Confirmation messages

• Business-specific notifications

• Failed transaction messages

• Success messages

Phrases can be configured using exact text or regular expressions.

You can also add a Phrase of Interest directly from Session Replay by selecting text displayed during a recorded session.

When the phrase subsequently appears, GermainUX records the event and makes it available for analysis.

🔔 Configure Watches & Alerts

Important application conditions can be monitored through GermainUX Watches and alerts.

For example, configure alerts for:

• Critical JavaScript errors

• Important Phrases of Interest

• Application failures

• Performance degradation

• Browser freezes

• Critical user journey failures

Alert conditions should focus on events that have meaningful user, application, or business impact rather than generating notifications for every technical event.

🔐 Configure Data Privacy & Exclusions

Review privacy settings before enabling MarkoJS monitoring in production.

GermainUX provides controls to exclude, mask, anonymize, or protect sensitive information captured through Real User Monitoring and Session Replay.

Review the MarkoJS application for information such as:

• Usernames

• Personal information

• Authentication data

• Form fields

• Customer information

• Business-sensitive information

• Application-specific confidential data

Configure the appropriate collection, masking, and exclusion rules according to your organization's security, privacy, and regulatory requirements.

🧪 Validate the Configuration

After changing the MarkoJS monitoring configuration, perform representative user journeys in the application.

For example:

Login → Navigate → Search → Perform Application Action → Logout

Verify that GermainUX captures the expected:

• User sessions

• User actions

• Session Replay

• JavaScript errors

• Network activity

• Performance events

• Phrases of Interest

• Application-specific events

Also verify that excluded or sensitive information is not collected.

ℹ️ Advanced Configuration

Additional RUM JS behavior can be customized through the UX Monitoring Profile and its Init Script.

Advanced configuration is available for capabilities such as:

• Session behavior

• JavaScript and console monitoring

• Performance monitoring

• JavaScript profiling

• Event processing

• Custom application events

• Application-specific monitoring rules

Use advanced configuration when the standard UX Monitoring Profile settings do not provide the application-specific behavior required for your MarkoJS environment.

ℹ️ Get More Information

Marko environments can vary significantly depending on storefront customization, extensions, integrations, infrastructure, and security requirements.

The GermainUX team can help configure the appropriate monitoring scope, privacy controls, analytics, alerts, and automation for your Marko environment.

Please contact us for any help.