You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2019/04/09 10:37:12 UTC
[jira] [Updated] (OAK-6836) OnRC report
[ https://issues.apache.org/jira/browse/OAK-6836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davide Giannella updated OAK-6836:
----------------------------------
Fix Version/s: 1.14.0
> OnRC report
> -----------
>
> Key: OAK-6836
> URL: https://issues.apache.org/jira/browse/OAK-6836
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Reporter: Valentin Olteanu
> Priority: Minor
> Labels: production
> Fix For: 1.12.0, 1.14.0
>
> Attachments: gcreport.png
>
>
> Currently, the information regarding an online revision cleanup execution is scattered across multiple log lines and partially available in the attributes of {{SegmentRevisionGarbageCollection}} MBean.
> While useful for debugging, this is hard to grasp for users that need to understand the full process to be able to read it.
> The idea would be to create a "report" with all the details of an execution and output it at the end - write to log, but also store it in the MBean, from where it can be consumed by monitoring and health checks.
> In the MBean, this would replace the _Last*_ attributes.
> In the logs, this could replace all the intermediary logs (switch them to DEBUG).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)