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 "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2016/07/12 11:55:20 UTC

[jira] [Resolved] (OAK-4542) PerfLogger should also allow a threshold to log at INFO

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

Vikas Saurabh resolved OAK-4542.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.6
                   1.4.5

> PerfLogger should also allow a threshold to log at INFO
> -------------------------------------------------------
>
>                 Key: OAK-4542
>                 URL: https://issues.apache.org/jira/browse/OAK-4542
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            Reporter: Vikas Saurabh
>            Assignee: Vikas Saurabh
>            Priority: Minor
>              Labels: candidate_oak_1_0, candidate_oak_1_2, monitoring, performance
>             Fix For: 1.4.5, 1.5.6
>
>
> Currently, {{PerfLogger}} logs at DEBUG if time spent in operation is more that threshold ms.
> We should also be able to have a second level threshold of time, beyond which the log should happen at INFO. It helps to catch cases for which the timing gets too poor at the onset of some performance issue and by the time of investigation (opportunity to add DEBUG logger) is too late already.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)