Logging
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.
Showing artifacts, examples and content with confirmed Standard ABAP applicability. View All ABAP
Overview
No SAP artifact is confirmed here for Standard ABAP.
A Standard ABAP coverage assessment has not been written. View all flavors
Gives logger objects a common interface across targets such as an internal table, the Application Log and the job log, so logging can be injected rather than hard-wired into application code.
Wraps the Business Application Log with a chainable factory interface: a header object collects text, messages and exceptions before a call to persist saves them.
Saves each function module call's parameters as JSON in a single log table, searchable by function module and field value, and reprocesses a saved call like WE19 does for an IDoc.
A Standard ABAP coverage assessment has not been written. View all flavors
Artifacts
Details
Coverage
For your agent
- Ref
capability:logging- JSON
- /capabilities/logging.json
- MCP
- Connecting an agent