Logging
In a UI5 app the running code is in the user's browser, so what it logs lands in that browser's console. The framework and the application write to one client-side log, and the question on this door is what reaches a developer who is not at that browser.
Overview
@openui5/sap.ui.core The OpenUI5 core: the module loader, the MVC runtime, data binding, routing, theming and the test stack, which is everything a UI5 app does before a single community package is added.
Not covered: In the browser. The log is read in the console of the browser's developer tools, and getting entries anywhere else is a listener the application registers and writes; the API documentation names sending them to a server as one use for that listener.
openui5-error-collectoropenui5-error-collectorA UI5 library that collects a running app's JavaScript errors, unhandled Promise rejections and UI5 log events, and can post them to a backend with navigator.sendBeacon.independent, ui5 gathers plain JavaScript errors, unhandled Promise rejections, sap/base/Log events and Reporting API errors, from before the UI5 bootstrap on, and posts them to a configured server with navigator.sendBeacon. SRBJSLoggersrbjsloggerA browser JavaScript logger whose log, warn and error calls write prominent output to the console, loaded into a UI5 app through index.html or the manifest's resources.independent, ui5 stays in the console and makes an application's own output stand out there, with a scope and a topic on every message and a command that logs the browser and screen details, optionally as a QR code.
Artifacts
Details
Coverage
For your agent
- Ref
capability:logging- JSON
- /capabilities/logging.json
- MCP
- Connecting an agent