Skip to main content
Availability2014.1 or later

8. Configure Form and Workflow Monitoring

Key forms and workflows

23. Configure Dashboards

Views for site teams

24. Validate the Configuration

Confirm monitoring is active

Troubleshooting

Resolve WordPress setup issues
Configuring Monitoring for WordPress with GermainUX: User Experience, Performance, and Error Analysis Configure GermainUX to analyze user experience, availability, performance, errors, APIs, logs, database behavior, and supporting infrastructure for WordPress websites.

1. Open the UX Monitoring Profile

Go to: Germain Workspace > Settings > Analytics > UX Monitoring Profiles Select the UX Monitoring Profile created for the WordPress website.

2. Configure Real User Monitoring

Configure the browser telemetry required for the monitoring objectives.
  • User sessions
  • Page views
  • Navigation
  • Clicks
  • User interactions
  • Page performance
  • Browser performance
  • Network requests
  • JavaScript errors
  • Customer-defined events
Enable only the monitoring required for the website.

3. Configure Session Replay

Configure Session Replay for the selected profile.
  • Session Replay enabled or disabled
  • Session timeout
  • Maximum recording duration
  • Behavior when username changes
  • IP exclusions
  • Included IP ranges
  • Username exclusions
  • Headless-browser exclusions
Global settings are available under: Germain Workspace > Settings > System > UX and Session Replay Settings

4. Configure Privacy

Configure masking, anonymization, and exclusions before production rollout.
  • Passwords
  • Authentication tokens
  • Names
  • Email addresses
  • Phone numbers
  • Addresses
  • Account information
  • Sensitive form fields
  • Restricted content
  • URL parameters containing identifiers
Collect only information required for the monitoring use case.

5. Configure Click Monitoring

Monitor:
  • Standard clicks
  • Dead clicks
  • Error clicks
  • Rage clicks
Use these signals to identify:
  • Unresponsive controls
  • Repeated attempts
  • JavaScript errors
  • Navigation problems
  • User frustration

6. Configure Performance Monitoring

Analyze:
  • Page-load time
  • User interaction time
  • Browser processing
  • Network-request duration
  • Server response time
  • REST API response time
Use page- and workflow-specific thresholds rather than applying one threshold to every page.

7. Configure JavaScript Error Monitoring

Monitor:
  • JavaScript exceptions
  • Browser console errors
  • HTTP failures
  • Failed network requests
  • Resource-loading failures
  • Theme-related browser issues
  • Plugin-related browser issues
  • Third-party script failures
Correlate errors with users, sessions, pages, interactions, browsers, and devices.

8. Configure Form and Workflow Monitoring

Define important WordPress workflows. Examples include:

Lead Generation

Landing PageFormSubmitConfirmation

Authentication

LoginAccountTarget Action

Registration

RegistrationConfirmationLogin

Content Conversion

ContentCall to ActionConversion
For each workflow, define:
  • Start
  • Milestones
  • Completion
  • Failure
  • Abandonment
Analyze:
  • Completion rate
  • Duration
  • Drop-off
  • Errors
  • Repeated actions
  • User friction
  • Performance delays

9. Configure REST API Monitoring — Optional

When GermainUX Engine monitors the WordPress REST API, configure:
  • Endpoint
  • HTTP method
  • Authentication
  • Headers
  • Request parameters
  • Timeout
  • Expected HTTP status
  • Response validation
  • Monitoring frequency
Use read-only requests whenever practical.

10. Configure WordPress Log Monitoring — Optional

Configure applicable log sources.
  • WordPress debug log
  • PHP logs
  • Web-server logs
  • Plugin logs
  • Integration logs
Create Rules to detect:
  • PHP errors
  • Plugin failures
  • Authentication errors
  • Application exceptions
  • Integration failures
  • Repeated warnings
  • New error patterns

11. Configure Database Monitoring — Optional

When database monitoring is deployed, analyze:
  • Availability
  • Connections
  • Query response time
  • Slow queries
  • Locks
  • Capacity
  • Errors
Correlate database performance with WordPress page and transaction performance.

12. Configure PHP Monitoring — Optional

When PHP telemetry is available, analyze application behavior such as:
  • Availability
  • Execution performance
  • Errors
  • Resource utilization
  • Slow server-side processing
Use PHP telemetry to determine whether slow WordPress responses originate in application execution.

13. Configure Infrastructure Monitoring — Optional

When infrastructure is accessible, monitor:
  • CPU
  • Memory
  • Disk
  • Filesystem
  • Network
  • Processes
  • Web server
  • Containers
  • Cloud resources
Analyze resource conditions together with WordPress performance.

14. Configure JS Profiler — Optional

Use GermainUX JS Profiler for deeper browser diagnostics. Analyze:
  • JavaScript execution
  • Slow functions
  • Browser processing
  • Network activity
  • Theme scripts
  • Plugin scripts
  • Third-party scripts
  • Browser freezes

15. Configure Synthetic Monitoring — Optional

Configure synthetic WordPress scenarios created with RPA Bot Recorder. Configure:
  • Scenario
  • Execution location
  • Schedule
  • Credentials
  • Timeout
  • Expected result
  • Failure condition
  • Alert
  • Maintenance window
Use controlled test accounts and data.

16. Configure KPIs

Configure KPIs appropriate for the WordPress monitoring objective.
  • User Session
  • User Interaction
  • Page Performance
  • JavaScript Error
  • HTTP Request
  • Synthetic Transaction
  • Application
  • Database
  • Infrastructure
Use KPIs available in the installed GermainUX version.

17. Configure Measures

Measures can include:
  • Users
  • Sessions
  • Page views
  • Interactions
  • Clicks
  • Errors
  • Error rate
  • Page-load time
  • Interaction response time
  • API response time
  • Workflow duration
  • Workflow completion rate
  • Database query time
  • CPU utilization
  • Memory utilization

18. Configure Analysis Dimensions

Analyze WordPress monitoring data by:
  • Application
  • Environment
  • User
  • Session
  • Page
  • URL
  • Interaction
  • Workflow
  • Browser
  • Device
  • Operating system
  • Geography
  • Error
  • API
  • Server
  • Database
  • Time period

19. Configure SLAs

Configure thresholds for conditions requiring attention. Examples:

Availability

Website Availability < Expected SLA

Page Performance

Page Load Time > Threshold

Interaction

Interaction Response Time > Threshold

JavaScript

JavaScript Error Rate > Threshold

API

WordPress API Response Time > Threshold

Database

Database Response Time > Threshold

Synthetic Monitoring

Critical Scenario = Failed

20. Configure Rules and Automated Analysis

Create Rules such as:
  • Slow Page + Slow API
  • Slow Page + Slow Database
  • JavaScript Error + Workflow Abandonment
  • Plugin Error + Increased HTTP Failures
  • Database Degradation + Slow Server Response
  • CPU Increase + Page Performance Degradation
  • New Error Pattern + Affected Users

21. Configure Alerts and Watches

Examples include: Website Unavailable → Alert Operations JavaScript Errors Increasing → Notify Engineering WordPress API Failure → Notify Application Team Database Performance Degradation → Notify Database and Application Teams Critical PHP Errors → Alert Support Synthetic Transaction Failure → Alert Operations GermainUX can trigger:
  • Alerts
  • Watches
  • Reports
  • Approved diagnostics
  • Approved automation

22. Configure Maintenance Windows

Define maintenance windows for expected changes such as:
  • WordPress upgrades
  • Theme upgrades
  • Plugin updates
  • PHP upgrades
  • Database maintenance
  • Hosting maintenance
Use maintenance windows to avoid unnecessary alerts during approved changes.

23. Configure Dashboards

User Experience Dashboard

Monitor:
  • Users
  • Sessions
  • Interactions
  • Dead clicks
  • Rage clicks
  • Error clicks
  • Session Replay
  • Page performance

Application Dashboard

Monitor:
  • Website availability
  • HTTP performance
  • REST API
  • PHP
  • Errors
  • Logs

Engineering Dashboard

Monitor:
  • JavaScript errors
  • JS Profiler
  • API performance
  • PHP errors
  • Plugin errors
  • Database performance

Infrastructure Dashboard

Monitor:
  • CPU
  • Memory
  • Disk
  • Network
  • Processes
  • Database
  • Web server

24. Validate the Configuration

Verify:
1

Sessions are created

2

Page views are captured

3

Navigation is captured

4

User interactions are captured

5

Click monitoring works as expected

6

Performance data is available

7

JavaScript errors are detected

8

Network requests are captured

9

Session Replay works

10

Sensitive data is protected

11

Workflows reconstruct correctly

12

REST API monitoring works when configured

13

Logs are collected when configured

14

Database monitoring works when configured

15

Infrastructure monitoring works when configured

16

Synthetic transactions execute correctly

17

SLAs evaluate correctly

18

Alerts and Watches operate as expected

Troubleshooting

No RUM Data

Verify:
  • RUM JS is installed.
  • Correct WordPress domain is configured.
  • Monitoring script loads successfully.
  • Browser requests to GermainUX are not blocked.
  • Caches contain the current monitoring configuration.
  • Test user or IP is not excluded.

RUM JS Loads More Than Once

Check all deployment locations, including:
  • Theme
  • Child theme
  • Header injector
  • Tag manager
  • Plugins
  • Custom JavaScript
Deploy RUM JS only once.

Session Replay Is Missing

Verify:
  • Session Replay is enabled globally.
  • Session Replay is enabled for the UX Monitoring Profile.
  • Privacy and exclusion settings are correct.
  • Monitoring data reaches GermainUX.

Theme or Plugin Update Breaks Monitoring

Verify whether the update changed:
  • Theme header
  • Script injection
  • DOM structure
  • JavaScript events
  • Content Security Policy
  • Caching
  • Optimization settings
Revalidate RUM JS after significant theme or plugin changes.

REST API Monitoring Fails

Verify:
  • Endpoint
  • HTTP method
  • Authentication
  • Credentials
  • Network connectivity
  • Expected response
  • Engine availability

Logs Are Missing

Verify:
  • Log path
  • File permissions
  • Engine access
  • Log rotation
  • Parser or monitoring configuration

Database Monitoring Is Missing

Verify:
  • Database hostname
  • Port
  • Credentials
  • Permissions
  • Network connectivity
  • Database monitor
  • Engine status

Get More Information

GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your Wordpress environment. 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.