Errors that affect Users

Feature

Germain has the ability to help you understand business impact of any errors on the end-user and business operations. In other words, Germain helps focus on the errors that impact Users of an application, and ignore the million other errors that don’t impact users.

The way to do this in Germain varies depending the monitored application and all customizable.

Examples for:

• Magento User Errors

• Oracle Siebel CRM User Errors

• Salesforce User Errors

Configuration

Magento User Errors

1. Enable Magento Error Monitoring (KPI/Component/..)

2. Add Portlet to display Magento Error
   Use “JavaScript Popup Dialog” KPI or any other KPI you have created.

3. Exclude Errors
   If you still need to ignore/exclude some of these errors, follow this process/example that is about excluding any errors that contain the string “…Required…”:

Oracle Siebel CRM User Errors

For Siebel, it is a bit more complicated to configure Germain to monitor the list of errors that affect Siebel Users, but it is possible by following the below process.

1. Build List of critical Oracle Siebel Errors

2. Enable KPI/Component/..

3. Add Portlet to display Oracle Siebel Errors
   Select “Siebel JavaScript Popup Dialog” and Use “Message” as pivot

   

   Result/Example:
   e.g. 1,044 Users were forced to re-logon due to a number of Siebel Application crash.

   

4. Exclude Oracle Siebel Errors
   If you still need to ignore/exclude some of these errors, follow this process/example that is about excluding any errors that contain the string “…Required…”:

Salesforce User Errors

1. Enable Salesforce User Error Monitoring (KPI/Component/..)

2. Add Portlet to display Salesforce User Errors
   User “JavaScript Popup Dialog” or any other KPI you have created and you will see Salesforce User Errors but if you you can also get the Salesforce Apex Error

3. Exclude Salesforce User Errors
   If you still need to ignore/exclude some of these errors, follow this process/example that is about excluding any errors that contain the string “…Required…”: