GermainUX can distinguish errors displayed to users from background errors that are not directly visible. This helps teams reduce noise and focus their analysis on failures that immediately affect the user experience.
👀 A user-facing error may appear as:
|
Visible indication |
|---|
|
An error message |
|
A warning or popup |
|
A failed action |
|
A broken page or component |
|
An HTTP request failure surfaced in the application |
|
Another visible indication that the software did not operate as expected |
Errors that are not visible to users should not automatically be ignored. Background errors may still affect integrations, performance, data accuracy, business processes, or downstream operations. They should be monitored separately and prioritized according to their technical and business impact.
💻 Display Only Errors Seen by Users
You can configure most GermainUX dashboard portlets to show only errors that were visible to users.
📊 Select an Error KPI
Use any KPI that captures the relevant errors, such as:
|
KPI |
Typical use |
|---|---|
|
Custom browser errors and application-specific error events. |
|
|
JavaScript console errors captured in the browser. |
|
|
Alerts, prompts, and confirmation dialogs displayed to users. |
|
|
Failed browser requests associated with user-facing issues. |
|
|
Custom Error KPI |
Errors captured through application-specific monitoring. |
📏 Select Measures
Choose measures that quantify the error’s frequency and impact, such as:
|
Measure |
Purpose |
|---|---|
|
Count |
Total number of matching errors. |
|
Count Unique User |
Number of users affected by the errors. |
|
Count Unique Session ID |
Number of sessions in which the errors occurred. |
Other measures can be added according to the KPI and the analysis required.
🔁 Select Pivots
Use a pivot that groups similar errors, typically:
|
Pivot |
|---|
|
Name |
|
Message |
Additional pivots—such as application, page, user, browser, device, or location—can help identify where the errors are concentrated.
🔎 Apply the User-Facing Error Filter
Add the following portlet filter:
User Error == true
This limits the portlet to errors identified by GermainUX as visible to users.
The current data field is named User Error. In this context, it represents a user-facing software error, not a mistake made by the user.
🔧 Technology-Specific Configuration
User-facing errors are detected differently depending on the application’s architecture, framework, and error-handling behavior.
Use the relevant configuration guide:
|
Technology |
Configuration Guide |
|---|---|
|
Magento |
|
|
Oracle Siebel CRM |
|
|
Salesforce |
|
|
Shopify |
📦 Application-Specific Detection
GermainUX provides preconfigured error-monitoring capabilities, but some application-specific configuration may be required.
Applications such as Salesforce, Oracle Siebel CRM, Magento, and Shopify use different frameworks, architectures, messages, and failure mechanisms. GermainUX must therefore be configured to recognize how each application presents errors to its users.
ℹ️ Get Help
The Germain Team can help you set this up. Contact GermainUX Support.
Service: Analytics
Feature Availability: 2022.1 or later