[jira] [Work logged] (ARTEMIS-2691) Improve critical analyzer LOG policy

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-2691?focusedWorklogId=415464&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-415464 ]

ASF GitHub Bot logged work on ARTEMIS-2691:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 03/Apr/20 12:22
            Start Date: 03/Apr/20 12:22
    Worklog Time Spent: 10m 
      Work Description: brusdev commented on pull request #3061: ARTEMIS-2691 Improve critical analyzer LOG policy
URL: https://github.com/apache/activemq-artemis/pull/3061
 
 
   Reset the critical component timer after the expiration to allow further LOG
   actions after the first expiration.
 
----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 415464)
    Remaining Estimate: 0h
            Time Spent: 10m

> Improve critical analyzer LOG policy
> ------------------------------------
>
>                 Key: ARTEMIS-2691
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2691
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>            Reporter: Domenico Bruscino
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The critical-analyzer only fires once but if the <critical-analyzer-policy> is set to LOG, it would make more sense to repeat the LOG action. This would help when doing log analysis after the issue was encountered.



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