Application Monitoring SAPUI5

[edbravo]

Hello everyone.

We are investigating if there is any way to monitor errors of a SAPUI5 App in this section once the App has been deployed.

Any way to send the bugs or similar?

We have been reviewing this section of the documentation

"Https://sapui5.hana.ondemand.com/sdk/#/topic/9f4d62c6648a423d85aaf2bfc2c7ddfe.html"

And using code to send error or Warning messages, but they only appear in the browser console.

Is there any configuration, any way, any code or activate something to be able to review the app once in the system?

Thanks in advance for your reply.

Greetings.

ED.

[Ivan-Mirisola · Accepted solution]

Hi edbravo,

Here are my two cents on the topic: applications based on HTML technology are running in a context that is out of reach from a centrally managed system - like BTP. Once BTP delivers the application resources (html, css, js, etc.) to your browser, it looses control over what is happening at the browser's context.

I remember a course on SAP Root Cause Analysis (RCA) where we learned how to troubleshoot such browser errors. Let's say a corporate user complains about an issue with an SAPUI5 app. So corporate support will initiate a RCA by installing a browser plugin that would capture all browser's errors and merge those into the back-end's logs. So as an analyst you would be able to figure out what was going on end-to-end. This is explained here:

https://help.sap.com/viewer/82f6dd44db4e4518aad4dfce00116fcf/LATEST/en-US/a56e3b810bd74f37b9468bc27f...

However, this would only make complete sense if your application makes calls to an on-prem system monitored by SAP Solution Manager. On other scenarios where there is no SolMan in place, I believe the same principles apply. However, RCA will never be a one tool place to go [silver boolet]. You have to perform the some type of work as described by michael.jess on his Mobile Services App RCA blog:

https://blogs.sap.com/2017/07/20/mobile-services-debugging-and-root-cause-analysis-walkthrough

Technically you could develop your own browser plugin to capture such errors and send them to an application bound to the log service in BTP for later analysis via Kibana. You application would implement a web service to receive the log message and throw them into the logging service via API calls. You could filter out known console error messages at the plugin stage before sending them to the BTP application. And later on, fine tune what is really important within your application.

In practical terms, I don't believe monitoring html applications for errors in such a way is really productive. RCA would be way more productive when you are inspecting an issue closely - case-by-case. And for that purpose, when troubleshooting web services running on BTP you could use Log Service and Kibana for RCA, just like explained on the above blog in conjunction with the browser's console while reproducing the error locally.

Furthermore, one could always make a case for SAP Software improvements via https://influence.sap.com/. Feel free to post your ideas there.

Hope this helps.

Best regards,
Ivan

[edbravo · Accepted solution]

Hi Ivan.

Thank you very much for all the context.

With this, I have to explain the matter to my superiors and see if it is worth it or not to continue with it.

Thank you again for your support.

Greetings.

EBZ.