Skip to main content
ComponentsEngineJS ProfilerMobile AppRPA Bot RecorderRUM ExtRUM JS
Availability2017.1 or later

GermainUX Components

Pick components for coverage

User Experience and Adoption

Track how users actually work

Recommended Configuration Sequence

Order to configure monitors

Security and Data Privacy

Checks before production enablement

​
Overview

Use these configuration guides to monitor and improve the performance, reliability, adoption, productivity, and user experience of Salesforce Classic and Lightning.

​
GermainUX Components

Depending on the required coverage, configuration may involve one or more GermainUX components:
Before configuring monitoring, complete Salesforce Monitoring Deployment.

​
Select What You Want to Monitor

​
User Experience and Adoption

​
User Monitoring and Session Replay

Configure Real User Monitoring to capture:
  • Salesforce sessions
  • Page views and navigation
  • User clicks and interactions
  • Search activity
  • User-facing errors
  • Browser and JavaScript errors
  • Page and interaction performance
  • Complete Session Replay
Use this configuration to understand what users experienced, reproduce problems, and identify the actions leading to an error, slow interaction, failed workflow, or abandonment. Configure User Monitoring and Session Replay

​
User Click Analysis

Configure the Salesforce actions that GermainUX should recognize and analyze as meaningful user interactions. This can include:
  • Opening a record
  • Saving or submitting a form
  • Creating a case
  • Updating an opportunity
  • Selecting an account
  • Completing a workflow step
  • Using a custom Salesforce component
The resulting data can support:
  • Adoption analysis
  • Feature-usage analysis
  • Workflow mining
  • Productivity measurement
  • Interaction-performance analysis
  • User segmentation
Configure User Click Analysis

​
User Feedback

Allow Salesforce users to submit feedback directly from the application. GermainUX can correlate the feedback with:
  • The affected user session
  • Session Replay
  • Recent interactions
  • Errors
  • Performance data
  • Workflow context
  • Technical telemetry
This reduces the effort required to understand and reproduce reported problems. Configure User Feedback

​
Error and Diagnostic Monitoring

​
Error Monitoring

Configure the detection and analysis of Salesforce errors, including errors presented to users. Correlate errors with:
  • User interactions
  • Session Replay
  • Browser events
  • Salesforce logs
  • Apex activity
  • API calls
  • Related services and integrations
Configure Error Monitoring

​
Apex Exception Monitoring

Capture Apex exceptions and analyze:
  • Exception type
  • Error message
  • Affected Apex class or trigger
  • User and transaction context
  • Frequency and trend
  • Related Salesforce and user-experience events
Configure Apex Exception Monitoring

​
Debug Log Monitoring

Collect Salesforce debug logs for deeper transaction and code-level analysis. Use debug logs to investigate:
  • Apex execution
  • SOQL queries
  • DML operations
  • Workflow and trigger behavior
  • Governor
  • SOQL queries
  • DML operations
  • Workflow and trigger behavior
  • Governor-limit consumption
  • Exceptions
  • Slow transactions
Because debug logging can generate significant data, configure it only for the users, components, and periods required for the investigation. Configure Debug Log Monitoring

​
Salesforce Log Monitoring

Configure broader collection and analysis of applicable Salesforce logs. Use log monitoring to detect:
  • Errors
  • Warnings
  • Failed operations
  • Performance degradation
  • Integration problems
  • Security or administrative activity
Configure Salesforce Log Monitoring

​
Apex Code Monitoring

Configure Apex monitoring to analyze Salesforce code execution and identify:
  • Slow Apex transactions
  • Slow classes or methods
  • Trigger delays
  • SOQL performance
  • Excessive query volume
  • DML activity
  • Governor-limit risks
  • Exceptions and failed transactions
Apex telemetry can be correlated with the Salesforce interaction that initiated the transaction, helping teams move from an affected user session to the related server-side execution. Configure Apex Code Monitoring

​
Salesforce Operations and Availability

​
Instance Status Monitoring

Monitor the availability and status of the Salesforce instance used by your organization. Use this data to:
  • Detect Salesforce service degradation
  • Distinguish Salesforce-wide issues from organization-specific problems
  • Correlate instance incidents with user errors or slow performance
  • Notify operations teams when service status changes
Configure Instance Status Monitoring

​
Salesforce Statistics

Collect operational and usage statistics to understand Salesforce activity, capacity, and trends. The available statistics depend on the Salesforce APIs and permissions enabled for the integration. Configure Salesforce Stats Monitoring

​
Omni-Channel Monitoring

Monitor Salesforce Omni-Channel activity to analyze:
  • Agent availability
  • Work assignment
  • Routing
  • Queue behavior
  • Capacity
  • Acceptance and handling
  • Delays affecting service representatives or customers
Configure Omni-Channel Monitoring

​
Events, Audit, and Administrative Changes

​
Real-Time Event Monitoring

Configure Salesforce real-time events when timely detection is required. Depending on the enabled Salesforce features and licenses, events can help monitor:
  • User activity
  • API activity
  • Authentication
  • Data access
  • Security events
  • Application behavior
  • Operational changes
Configure Real-Time Event Monitoring

​
Audit Monitoring

Monitor Salesforce administrative and configuration changes to establish who changed what and when. Audit data can help investigate:
  • Unexpected application behavior
  • Configuration drift
  • Permission changes
  • Deployment-related problems
  • Security events
  • Changes correlated with a new performance or user-experience issue
Configure Audit Monitoring For a new Salesforce environment, configure monitoring in this order:
1

Complete the Salesforce deployment prerequisites

2

Configure User Monitoring and Session Replay

3

Apply masking, anonymization, and exclusion rules

4

Configure meaningful Salesforce user actions

5

Enable user-facing error detection

6

Configure the Salesforce Engine integration

7

Enable Apex, exception, log, event, audit, status, and statistics monitoring as required

8

Configure critical Salesforce workflows

9

Build or customize the required dashboards

10

Define SLAs, alerts, reports, and automated actions

11

Validate monitoring with representative users

12

Confirm security, privacy, data-volume, and retention settings before the production rollout

​
Validate the Configuration

After configuration, confirm that GermainUX receives the expected data.

​
User-Experience Validation

Verify that:
  • Salesforce sessions appear.
  • Users and application profiles are identified correctly.
  • Navigation and meaningful user actions are captured.
  • Interaction durations are available.
  • Errors are detected.
  • Session Replay contains the expected activity.
  • Sensitive values are masked or excluded.

​
Server-Side Validation

Verify that:
  • The Salesforce OAuth connection succeeds.
  • The correct organization and instance are monitored.
  • Apex, exception, log, event, audit, and statistics data appear as configured.
  • The dedicated integration user has only the approved permissions.
  • API limits and data-collection volume remain acceptable.

​
Correlation Validation

When both browser and Salesforce monitoring are enabled, confirm that GermainUX can relate:
  • User interactions to server-side activity
  • Errors to the affected sessions
  • Slow actions to Apex, SOQL, API, or integration delays
  • Workflow problems to the responsible UX or technical events

​
Security and Data Privacy

Before production enablement:
  • Use a dedicated Salesforce integration account.
  • Grant only the OAuth scopes and Salesforce permissions required.
  • Configure masking, anonymization, and exclusions.
  • Avoid collecting credentials, tokens, health information, payment data, or other sensitive values unless explicitly required and protected.
  • Limit debug logging to the users and periods needed.
  • Review Salesforce API usage and storage volume.
  • Validate access to Session Replay and other user-level data.
  • Align data retention with organizational policies.

​
Additional Resources

Troubleshooting Tips

Read more

Management

More Management Features

​
Get Help

Contact GermainUX Support

The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

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.