> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure User Error Monitoring

> Errors that are not visible to users should not automatically be ignored.

Service
`Analytics`

Availability
2022.1 or later

> **[Display Only Errors Seen by Users](#display-only-errors-seen-by-users)**
>
> Restrict portlets to visible errors

> **[Technology-Specific Configuration](#technology-specific-configuration)**
>
> Guides by framework and architecture

> **[Application-Specific Detection](#application-specific-detection)**
>
> Salesforce, Siebel, Magento, Shopify

> [!NOTE]
>
> 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:

* 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 |
| - | - |
| [AI Error Analysis](https://docs.germainux.com/main/ai-kpis-pivots-measures.md) | An AI-generated analysis of error events to help teams quickly understand errors and support further investigation. |
| [Browser Event](https://docs.germainux.com/main/kpis-web-analytics.md) | Custom browser errors and application-specific error events. |
| [JavaScript Console Event](https://docs.germainux.com/main/kpis-web-analytics.md) | JavaScript console errors captured in the browser. |
| [JavaScript Popup Dialog](https://docs.germainux.com/main/kpis-web-analytics.md) | Alerts, prompts, and confirmation dialogs displayed to users. |
| [Outbound HTTP Request](https://docs.germainux.com/main/kpis-web-analytics.md) | Failed browser requests associated with user-facing issues. |
| [Custom Error KPI](https://docs.germainux.com/main/custom-insights.md) | 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:

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

```text theme={null}
User Error == true
```

![Configure User Error Monitoring: Apply the User-Facing Error Filter](https://mintcdn.com/germain-ux/npHkPTFCfiH3hzwe/images/main/configure-user-error-monitoring/image-20240513-181944.png?fit=max\&auto=format\&n=npHkPTFCfiH3hzwe\&q=85\&s=26e684a80c51b10003e5056c6722c5b3)

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** | [Configure Magento User Errors](https://docs.germainux.com/main/deploy-critical-user-error-monitoring-for-magento.md) |
| **Oracle Siebel CRM** | [Configure Siebel User and Object Manager Errors](https://docs.germainux.com/main/siebel-error-monitoring-configuration.md) |
| **Salesforce** | [Configure Salesforce User Errors](https://docs.germainux.com/main/error-monitoring-for-salesforce-cloud-configure.md) |
| **Shopify** | [Configure Shopify User Errors](https://docs.germainux.com/main/error-monitoring-for-shopify-configure.md) |

## 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.

## Additional Resources

> **[Troubleshooting Tips](https://docs.germainux.com/main/germain-enterprise-troubleshooting.md)**
>
> Read more

> **[Manage GermainUX health](https://docs.germainux.com/main/germain-health.md)**
>
> Read more

> **[Management](https://docs.germainux.com/main/management.md)**
>
> More Management Features

## Get Help

> **[Contact GermainUX Support](https://docs.germainux.com/main/support.md)**
>
> 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.