[ https://issues.apache.org/jira/browse/ARTEMIS-2512?focusedWorklogId=324475&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-324475 ]
ASF GitHub Bot logged work on ARTEMIS-2512: ------------------------------------------- Author: ASF GitHub Bot Created on: 07/Oct/19 16:17 Start Date: 07/Oct/19 16:17 Worklog Time Spent: 10m Work Description: brusdev commented on pull request #2857: ARTEMIS-2512 Move the LocalMonitor tick log URL: https://github.com/apache/activemq-artemis/pull/2857 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. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 324475) Remaining Estimate: 0h Time Spent: 10m > 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)