jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vikas Saurabh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-4542) PerfLogger should also allow a threshold to log at INFO
Date Tue, 12 Jul 2016 11:09:20 GMT

    [ https://issues.apache.org/jira/browse/OAK-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15372700#comment-15372700

Vikas Saurabh commented on OAK-4542:

Done in trunk. [r1752273|https://svn.apache.org/r1752273] added/refactored more tests according
to existing implementation. [r1752274|https://svn.apache.org/r1752274] implements the change,
update/add tests.

> 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, candidate_oak_1_4, monitoring,
> Currently, {{PerfLogger}} logs at DEBUG if time spent in operation is more that threshold
> 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

View raw message