Uploaded August 2022 | Updated November 2026, 1 day ago
Today, all JavaScript errors in a Fiori/UI5 app live and die in the browser. They are not logged in anywhere else. They mostly go unnoticed until a user complains that something is not working. A developer needs to ask users to provide screenshots from DevTools or jump in a screen share session.
Services such as DataDog and LogRocket could help in this scenario, but pretty much nobody uses that in SAP. To close this gap, I have created a module that helps developers in capturing all frontend errors and sending them to a backend for proper logging. Having it in a logging system helps the Tech team to identify and fix issues earlier and faster.
The module, openui5-error-collector, is a simple plug&play with no dependencies. It's backend agnostic, one can send data to anywhere: SAP Gateway, SAP Solution Manager, SAP BTP Alert Notification Service, AWS CloudWatch, etc
Event: #UI5conHYBDIRD2022
Speaker: Mauricio Lauffer, SAP
---
00:00 Introduction
03:19 Overview of the OpenUI5 Error Collector
06:48 Capturing Errors Locally
11:24 Sending Capture Errors to the Backend
20:09 Demo: Using OpenUI5 Error Collector in BTP Cockpit
22:18 Is The Logger Always Active in Productive, Or Can It Be Activated On the Fly?
23:40 Is the Error Logging Module Only Available for OpenUI5 or Also for SAPUI5?
24:22 How Are the Errors Mapped to the Correct User?
25:52 Do You Plan to Add this Module to Best of UI5?
---
Resources:
GitHub: github.com/mauriciolauffer/openui5-error-collector
Today, all JavaScript errors in a Fiori/UI5 app live and die in the browser. They are not logged in anywhere else. They mostly go unnoticed until a user complains that something is not working. A developer needs to ask users to provide screenshots from DevTools or jump in a screen share session.
Services such as DataDog and LogRocket could help in this scenario, but pretty much nobody uses that in SAP. To close this gap, I have created a module that helps developers in capturing all frontend errors and sending them to a backend for proper logging. Having it in a logging system helps the Tech team to identify and fix issues earlier and faster.
The module, openui5-error-collector, is a simple plug&play with no dependencies. It's backend agnostic, one can send data to anywhere: SAP Gateway, SAP Solution Manager, SAP BTP Alert Notification Service, AWS CloudWatch, etc
Event: #UI5conHYBDIRD2022
Speaker: Mauricio Lauffer, SAP
---
00:00 Introduction
03:19 Overview of the OpenUI5 Error Collector
06:48 Capturing Errors Locally
11:24 Sending Capture Errors to the Backend
20:09 Demo: Using OpenUI5 Error Collector in BTP Cockpit
22:18 Is The Logger Always Active in Productive, Or Can It Be Activated On the Fly?
23:40 Is the Error Logging Module Only Available for OpenUI5 or Also for SAPUI5?
24:22 How Are the Errors Mapped to the Correct User?
25:52 Do You Plan to Add this Module to Best of UI5?
---
Resources:
GitHub: github.com/mauriciolauffer/openui5-error-collector










