Logging
Seeing what a running service did, in a form something can read afterwards — levels, a formatter that suits a laptop and one that suits a log service.
Overview
com.sap.cds:cds-services-bom Logs through the Java logging facade under Spring Boot's configuration, with predefined loggers per runtime component and correlation ids.
Not covered: At lines of text. Correlating them across handlers and services is tracing, which is telemetry's entry, not this one.
No community artifact is documented here.
On BTP logging is where the lines go rather than how they are written: SAP Application Logging serviceSAP Application Logging service for SAP BTPCollects an application's log lines from Cloud Foundry or Kyma into a searchable Kibana, for the retention the plan sets.sap official, btp collects an application's output from Cloud Foundry or Kyma into a searchable Kibana.
Present, not yet described.
Not covered: At collection and whatever retention the plan sets. Nothing here decides what an application writes, and a log service is not an audit trail — that is audit loggingAudit loggingRecording who touched personal or sensitive data, in a form an auditor accepts, without hand-writing it in every handler. It is often confused with application logging, which records what the code did rather than who accessed what.SAP only.
SAP's side is the services that collect and keep an application's output: SAP Application Logging serviceSAP Application Logging service for SAP BTPCollects an application's log lines from Cloud Foundry or Kyma into a searchable Kibana, for the retention the plan sets.sap official, btp and SAP Cloud LoggingSAP Cloud LoggingAn instance-based observability service built on OpenSearch that stores and analyses logs, metrics and traces from Cloud Foundry, Kyma, Kubernetes and other runtime environments.sap official, btp, which also takes metrics and traces. The community adds command lines that read Cloud Foundry logs from a developer's machine, as cf-logs@saptools/cf-logsA command line and typed Node.js library that fetches and streams the logs of one Cloud Foundry app and parses them into structured rows.independent, btp does for one app and cf-tail@saptools/cf-tailA command line that tails every started app in a Cloud Foundry space at once and merges their logs into one timeline by timestamp, with filters by level, tenant, router status and time window.independent, btp does for every started app in a space.
On the ABAP door logging code mostly wraps the application log in an object-oriented API, as abap-log by Fabian LupaFabian Lupamaintains 1 entry, contributed to 7 entries does among other targets. The rest write elsewhere: a function module's parameters to a table of their own, or entries to Fluentd, Graylog or Loki outside the system.
The application log records application-specific events: log objects are defined in SLG0, applications write entries through SAP function modules, and SLG1 analyses the log. In ABAP Cloud the Application Log API is the class CL_BALI_LOG.
Not covered: Inside the system. Logs are read in SLG1; the page checked describes the application log's own function modules and transaction.
Object-oriented wrappers around the application log, as abap-logabap-logA logging library for ABAP with one logger interface in front of several targets, from the Application Log and the job log to database tables, files and the Eclipse console.independent, abap by Fabian LupaFabian Lupamaintains 1 entry, contributed to 7 entries and abap-cloud-loggerabap-cloud-loggerA logging library for ABAP Cloud that wraps the released class CL_BALI_LOG in a chainable logger, collecting exceptions, messages and tables, with a stopwatch and a sticky context tag.independent, abap do; exporters that send its entries to outside log systems such as Graylog or Loki, as abap-log-exporterabap-log-exporterExports SAP NetWeaver logs from the Business Application Log to an external log system such as Graylog or Loki, converting entries to GELF or Loki format through a separately configured reader, converter and connector.independent, abap does; and a port for ABAP transpiled to JavaScript, open-abap-balopen-abap-balApplication logging for ABAP code transpiled to JavaScript and run on Node.js, one of the runtime libraries open-abap.org lists.community org, abap from open-abapopen-abapmaintains 9 entriescommunity org.
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.
@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
Content
Show 8 more
Seen working
Details
Coverage
For your agent
- Ref
capability:logging- JSON
- /capabilities/logging.json
- MCP
- Connecting an agent