Configuration for Salesforce Classic, Lightning

⚙️ Configure Monitoring for Salesforce Classic and Lightning

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:

Component	Details
RUM Extension	Real User Monitoring and Session Replay
Engine	Salesforce APIs, events, logs, and server-side telemetry; plus other insights, alerts, reports, and corrective actions.
Mobile App	Real-time monitoring of Android applications and devices
JS Profiler	Advanced browser and JavaScript diagnostics
RPA Bot	Continuous synthetic monitoring

Before configuring monitoring, complete Salesforce Monitoring Deployment.

📋 Select What You Want to Monitor

Objective	Configuration guide
Understand the complete Salesforce user experience	User Monitoring and Session Replay
Analyze Salesforce user interactions and adoption	User Click Analysis
Collect and analyze Salesforce user feedback	User Feedback
Detect application errors shown to users	Error Monitoring
Monitor Apex execution and performance	Apex Code Monitoring
Detect Apex exceptions	Apex Exception Monitoring
Collect Salesforce debug logs	Debug Log Monitoring
Monitor Salesforce logs	Log Monitoring
Track configuration and administrative changes	Audit Monitoring
Monitor Salesforce real-time events	Real-Time Event Monitoring
Monitor Salesforce instance availability and health	Instance Status Monitoring
Collect Salesforce usage and operational statistics	Salesforce Stats Monitoring
Monitor Omni-Channel activity and performance	Omni-Channel Monitoring

👥 User Experience and Adoption

🎥 User Monitoring and Session Replay

Configure Real User Monitoring to capture:

Item
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:

Action
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:

Outcome
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:

Correlation
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:

Source
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:

Attribute
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:

Investigation
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:

Detection
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:

Issue
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:

Use
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:

Metric
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:

Event
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:

Investigation
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

▶️ Recommended Configuration Sequence

For a new Salesforce environment, configure monitoring in this order:

Complete the Salesforce deployment prerequisites.
Configure User Monitoring and Session Replay.
Apply masking, anonymization, and exclusion rules.
Configure meaningful Salesforce user actions.
Enable user-facing error detection.
Configure the Salesforce Engine integration.
Enable Apex, exception, log, event, audit, status, and statistics monitoring as required.
Configure critical Salesforce workflows.
Build or customize the required dashboards.
Define SLAs, alerts, reports, and automated actions.
Validate monitoring with representative users.
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:

Check
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