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

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

                Author: ASF GitHub Bot
            Created on: 16/Oct/24 20:47
            Start Date: 16/Oct/24 20:47
    Worklog Time Spent: 10m 
      Work Description: jbertram opened a new pull request, #5303:
URL: https://github.com/apache/activemq-artemis/pull/5303

   The broker uses unique IDs for logging statements. As logging changes over 
time we need a way to "retire" these IDs (e.g. when certain logging statements 
are no longer needed) to ensure they are not used
   
   This commit removes all the logging methods which are no longer used and 
"retires" the corresponding ID (i.e. adds them to the `retiredIDs` list for 
that LogBundle).




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

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

> Add ability to identify retired IDs in log annotations
> ------------------------------------------------------
>
>                 Key: ARTEMIS-5110
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5110
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The broker uses unique IDs for logging statements. As logging changes over 
> time we need a way to "retire" these IDs (e.g. when certain logging 
> statements are no longer needed) to ensure they are not used again in the 
> future (or perhaps put back into the rotation after a certain amount of time).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to