You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (Jira)" <ji...@apache.org> on 2026/04/30 12:35:00 UTC

[jira] [Updated] (SLING-13188) Provide an optional in-memory store of recent log events

     [ https://issues.apache.org/jira/browse/SLING-13188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu updated SLING-13188:
------------------------------------
    Attachment: screenshot-1.png

> Provide an optional in-memory store of recent log events
> --------------------------------------------------------
>
>                 Key: SLING-13188
>                 URL: https://issues.apache.org/jira/browse/SLING-13188
>             Project: Sling
>          Issue Type: New Feature
>          Components: Commons
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>            Priority: Major
>             Fix For: Commons Log 6.0.6, Commons Log 5.5.2
>
>         Attachments: screenshot-1.png
>
>
> It is sometimes useful to query recent log event, for instance in developer tools. It is currently possible to do so by registering an Appender OSGi service ( https://sling.apache.org/documentation/development/logging.html#appenders-as-osgi-services-1 ) but that has two drawbacks:
> - it is a common concern that gets duplicated across multiple consumers
> - it binds the consumers to logback APIs
> The commons log bundle should provide an optional comoponent that exposes the recent log entries without forcing the consumer to bind to logback APIs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)