You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/11/16 05:28:00 UTC
[jira] [Work logged] (ARTEMIS-4507) Make critical analyzer logging consistent
[ https://issues.apache.org/jira/browse/ARTEMIS-4507?focusedWorklogId=890853&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-890853 ]
ASF GitHub Bot logged work on ARTEMIS-4507:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Nov/23 05:27
Start Date: 16/Nov/23 05:27
Worklog Time Spent: 10m
Work Description: jbertram opened a new pull request, #4679:
URL: https://github.com/apache/activemq-artemis/pull/4679
(no comment)
Issue Time Tracking
-------------------
Worklog Id: (was: 890853)
Remaining Estimate: 0h
Time Spent: 10m
> Make critical analyzer logging consistent
> ------------------------------------------
>
> Key: ARTEMIS-4507
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4507
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently if the {{critical-analyzer-policy}} is {{HALT}} or {{SHUTDOWN}} the log message is at {{ERROR}}. However, if the policy is {{LOG}} then the message is logged at {{WARN}}. All policies should log at {{ERROR}} to be consistent.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)