PackagePackageA library you install and call yourself.See every one →What this type is →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
abap-fluentd
A Fluentd client written in ABAP for sending log lines from an ABAP system to a Fluentd collector, where entries are flushed with an explicit COMMIT WORK.
Fluentd client in ABAP: the sample usage shows an OData handler class creating a logger against an instance name, zcl_fdlog with iv_inst_name = 'ZHELLO_ODATA', and calling it to record each entity-set request and an error such as a developer not found. Log entries have to be flushed with an explicit COMMIT WORK, which the README calls out in capitals as the step not to forget. It stops at sending entries into Fluentd; what happens to them after that is Fluentd's own pipeline, which the README illustrates with a Kibana screenshot.
Facts
Last pushLicenceMIT
Where it sits
Lives in
Provides
Requires
abapGitabapGitInstalls the repository into the ABAP system; the README gives abapGit as the way to clone or import it.
Who is behind it
Chairat Onyaem (Par)Chairat Onyaem (Par)Maintains this
In the atlas: maintains 2, contributes to 2@pacroymaintainer
In the atlas: maintains 2, contributes to 2@pacroymaintainer
Before choosing this
Signals
ActivityQuietNo published releases; repository quiet for 96 months
It publishes no releases, and its repository has been quiet for at least 24 full months. This may be normal for stable software; check whether its current state still fits your use.
What it declares
Every artifact
- Type
- Package
- Origin
- Independently maintained
As a package
- Where it runs
- Inside its host
- Distributed through
- abapGit
Connections
Group by
NodeRelationBasis
Functional
LoggingLoggingSeeing what a running service did, in a readable formSAP only
provides
stated
provides Logging
Sends log lines from ABAP application code, such as an OData handler, to a Fluentd collector using a class-based logger interface.
“Fluentd client in ABAP”“ao_fdlog = NEW zcl_fdlog( iv_inst_name = 'ZHELLO_ODATA' ).”“ao_fdlog->i( |GET { iv_entity_set_name }| ).”
Seeing what a running service did, in a readable form
Technical
abapGitabapGitGit client written in ABAP that runs inside the systemcommunity org, abap
needs
stated
needs abapGit
Installs the repository into the ABAP system; the README gives [abapGit](artifact:abapgit-abapgit) as the way to clone or import it.
“Clone or import using [abapGit](https://github.com/larshp/abapGit)”
Git client written in ABAP that runs inside the system
Download
README
quoted from pacroy/abap-fluentd under MIT, readpacroy/abap-fluentd/README.mdthe maintainer’s wordsOn GitHub
Fluentd client in ABAP
Clone or import using abapGit
Sample Usage
CLASS zcl_zhello_dpc_ext IMPLEMENTATION.
METHOD constructor.
super->constructor( ).
ao_developer = NEW zcl_hello_developer_persist( ).
ao_fdlog = NEW zcl_fdlog( iv_inst_name = 'ZHELLO_ODATA' ).
ENDMETHOD.
METHOD developerset_get_entityset.
ao_fdlog->i( |GET { iv_entity_set_name }| ).
et_entityset = ao_developer->select_developer_set( ).
COMMIT WORK.
ENDMETHOD.
METHOD developerset_get_entity.
ao_fdlog->i( |GET { iv_entity_name }| ).
ao_fdlog->i( |Key: { /ui2/cl_json=>serialize( it_key_tab ) } | ).
DATA(lo_message) = mo_context->get_message_container( ).
er_entity = ao_developer->select_developer( CONV #( it_key_tab[ name = 'ID' ]-value ) ).
IF ( er_entity IS INITIAL ).
lo_message->add_message_text_only(
EXPORTING
iv_msg_type = 'E'
iv_msg_text = 'Developer not found' ).
ao_fdlog->e( |Developer not found| ).
RAISE EXCEPTION TYPE /iwbep/cx_mgw_busi_exception
EXPORTING
textid = /iwbep/cx_mgw_busi_exception=>resource_not_found
message_container = lo_message.
ENDIF.
COMMIT WORK.
ENDMETHOD.
ENDCLASS.DO NOT FORGET TO COMMIT WORK
Others providing
Compare all 11 on the Logging page →LoggingLoggingSeeing 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.SAP only
- ABAP-LoggerABAP-LoggerA logging library for ABAP that records messages into the standard Application Log (BC-SRV-BAL) and displays them from there, installed through abapGit on ABAP 702 or higher.independent, abapLogging library for ABAP over the Application Log
- 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, abapExports Business Application Log entries to Graylog or Loki
- ABAP-PRCABAP-PRCA framework for custom multi-step ABAP processes: a process class declares the states, and the framework runs each document through them and monitors the run.independent, abapFramework for multi-step ABAP processes with monitoring
- 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, abapABAP logging library with one interface across output targets
- ABAP_LOGGINGABAP_LOGGINGAn object-oriented wrapper around SAP's Business Application Log (BAL) for ABAP NetWeaver, chaining texts, messages and exceptions onto a log header that persists in its own or the same connection.independent, abapObject-oriented wrapper around the Business Application Log
- 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, abapChainable logger for ABAP Cloud around CL_BALI_LOG
- abap-fm-loggerabap-fm-loggerA logger for ABAP function modules (RFC) that stores each call's parameters as JSON in one table, with a viewer report to search the log and reprocess a record, akin to WE10 and WE19.independent, abapLogger storing RFC function module call parameters as JSON
- 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, abapApplication logging for ABAP transpiled to JavaScript on Node.js
- sap-usi-logging-apisap-usi-logging-apiAn object-oriented encapsulation around SAP's Application Log (transaction SLG1), controlled by customizing, with attachable data containers that SLG1 shows behind a detail button.independent, abapObject-oriented wrapper around SAP's Application Log (SLG1)
- abap-message-loggerabap-message-loggerA message logger for ABAP Cloud that collects T100 messages, BAPIRET2 structures, exceptions and plain text before saving them to the Application Log.independent, abapMessage logger for ABAP Cloud that saves to the Application Log
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
discovered viadotabap
first seen in the atlas
ecosystem and domainabap, operations-and-runtime
abaplint
issues under its own abaplint configuration605
lines2,172
statements1,222
objects11
files26
analysed, master
abaplint version2.120.84
read fromabaplint.app,
History in the atlas
- First seen.
For your agent
- Ref
artifact:pacroy-abap-fluentd- JSON
- /artifacts/pacroy-abap-fluentd.json
- MCP
- Connecting an agent