[jira] [Commented] (ARTEMIS-2512) Move the LocalMonitor tick log

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946186#comment-16946186 ] 

ASF subversion and git services commented on ARTEMIS-2512:
----------------------------------------------------------

Commit 615fb6400855278acc1c36380f1b351b0c1505b8 in activemq-artemis's branch refs/heads/master from brusdev
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=615fb64 ]

ARTEMIS-2512 Move the LocalMonitor tick log

The LocalMonitor tick log is very useful to establish a "heartbeat" log
statement. It is moved into its own logger from PagingManager logger,
which is too verbose to leave activated indefinitely in production.


> Move the LocalMonitor tick log
> ------------------------------
>
>                 Key: ARTEMIS-2512
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2512
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>            Reporter: Domenico Bruscino
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Can we please move the logging below to its own logger. This is very useful logging to establish a "heartbeat" log statement (logging consistently every 5 seconds) when investigating potential CPU starvation or "pause" issues.
> {noformat}
> ...TRACE [org.apache.activemq.artemis.core.paging.impl.PagingManagerImpl] Tick from store...
> {noformat}
> Right now, it is TRACE on the PagingManager logger. That includes other log statements that is too verbose to leave activated indefinitely in production.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)