You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Domenico Bruscino (Jira)" <ji...@apache.org> on 2019/10/07 15:44:00 UTC

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

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

Domenico Bruscino updated ARTEMIS-2512:
---------------------------------------
    Summary: Move the LocalMonitor tick log  (was: Split the LocalMonitor tick log into its own logger)

> 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
>
> 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)